Harness-library dossier · updated 6 Oct 2026
Marketing Agent OS: portable skills, not a marketing application.
Marketing Agent OS provides marketing-oriented skills and related materials for an approved host harness. The library does not establish the host’s permissions, credentials, network access, approvals, logs, or recovery controls.
What the checked material supports
Selected-skill projection.
Architecture describes selected skills being projected into a target harness directory, with tracked upstream snapshots excluded. The project documents staging and atomic replacement; exact copied files, collision behavior, backups, and rollback were not verified here.
Policy is not an enforcement system.
SECURITY says external and persistent actions need authorization and optional connectors inherit host/provider security. The audit did not establish a built-in sandbox, approval engine, credential vault, network allowlist, or runtime audit log.
The README’s count of 236 installable skills conflicts with the architecture/compatibility count of 235 portable skills. Treat both as project claims until the current catalogue and intended output are reviewed.
What adoption requires
- Choose and approve the host harness, its tool permissions, filesystem scope, network access, credentials, logs, retention, and recovery.
- Review the selected skill directories and installer source before a write; use a small selected set rather than bulk installation.
- Verify retained notices and provenance for the particular material you plan to use.
- Use no client data, secrets, configured connectors, or external actions in the first evaluation.
Conditional choice
For a first evaluation, use an empty non-client repository and fictional facts. Review only a local planning draft and its file diff, then clean up. Do not send, post, spend, mutate accounts, use production credentials, expose webhooks, or schedule work.
6 October install-test gate
The one-skill, project-scoped install test did not run. The intended pinned checkout was unreachable (git ls-remote exited 128 after DNS failure), and unshare -n could not create a network-denied boundary (exit 1, operation not permitted). No skill or target was selected, and no dry-run, install or file diff was observed. See the permanent test-gate report. Keep the first evaluation proposed, not performed, until both gates work.
Evidence and limits
Visible history and a private vulnerability-reporting route are limited maintenance/process signals. README claims about tests, CI, and compatibility were not reproduced. See the permanent provenance and host-harness boundary audit for sources, explicit unknowns, and the bounded evaluation plan.
For the separate draft → approval → optional action responsibilities, read the 28 Sep cross-layer handoff synthesis. It is not a tested integration or a recommendation to connect these products.