Marketing Skills
Deploy Marketing Skills as versioned agent content, not another server
Plan installation scope, referenced files, context migration and reversible updates for a Markdown-based skill library.
What you will learn
- Deploy skill directories and references, not a server.
- Record resolved revisions and avoid duplicate installs.
- Prove loading with a known task before retiring a version.
Before you start
- Basic Markdown and repository navigation
- An owned page and a factual product brief
Explain the chapter’s workflow boundary and check its evidence or proposed acceptance task.
Key takeaways
- Deploy skill directories and references, not a server.
- Record resolved revisions and avoid duplicate installs.
- Prove loading with a known task before retiring a version.
Install an artifact, not a web service
There is no universal container or listening port to configure for reading these skills. The deployment artifact is a set of skill directories and their references, consumed by a compatible agent. The README offers installer, plugin, manual-copy and submodule approaches. Select the approach that your actual host supports rather than combining them and creating duplicate definitions.
The documented discovery command is npx skills add coreyhaines31/marketingskills --list. It invokes an external installer and is not a command we executed during review. Listing is a useful preparatory step, but an unpinned installer and branch name are not a reproducible installation record. Record the resolved installer and repository versions in your own change process.
Preserve references and migrate context carefully
A SKILL.md file can link to references that hold detailed procedures. Copying only the top-level text can leave a superficially present skill with missing supporting material. Inspect relative links and retain required files. Keep secrets, customer exports and account tokens outside the installed skill tree and outside the shared marketing context.
The inspected product-marketing workflow prefers .agents/product-marketing.md and checks older .claude locations and the product-marketing-context.md filename as fallbacks. Migration should reconcile versions and retain a recoverable copy. Do not apply the README’s broad legacy cleanup commands blindly to a directory that also contains your own unrelated skills.
Make upgrades observable and reversible
A reliable acceptance test asks the agent which installed skill and context revision it used, then checks a small known task. Presence on disk is only an installation check; correct loading and useful output are separate checks. Keep the former version available until the pilot passes, especially when skill names or context locations changed.
The repository’s sync script aligns marketplace metadata, the plugin version and the README table. That maintenance automation does not upgrade every user installation and does not verify its host permissions. Our deployment manifest is a proposed checklist; no installed-agent upgrade, full plugin runtime or live publication was performed for this article.
Implementation steps
- 1
Inspect the selected skill and linked files.
- 2
Choose one host-supported installation method.
- 3
Reconcile existing context without broad deletion.
- 4
Run a known read-only task and record its loaded revisions.
Copy-ready example
{"repositoryCommit":"5b2c0007766c6a1cf1d53fd8fc73e979e0821022","pluginManifestVersion":"2.11.1","installerVersion":null,"hostLoadVerified":false,"contextBackupVerified":false}Frequently asked questions
What port does the skill library use?
Reading the library does not require its own server port. Optional integrations have separate deployment and authentication requirements.
Does a synchronized plugin version prove an upgrade worked?
No. It aligns repository metadata; verify the resolved installation and the host’s actual loading behavior separately.
Sources
- README.mdSource checked 2026-09-08
- LICENSESource checked 2026-09-08
- .claude-plugin/plugin.jsonSource checked 2026-09-08
- .github/scripts/sync-skills.jsSource checked 2026-09-08
- .github/workflows/sync-skills.ymlSource checked 2026-09-08
- .github/workflows/validate-skill.ymlSource checked 2026-09-08
- scripts/sync-partners.mjsSource checked 2026-09-08
- skills/product-marketing/SKILL.mdSource checked 2026-09-08
- skills/ai-seo/SKILL.mdSource checked 2026-09-08
- skills/seo-audit/SKILL.mdSource checked 2026-09-08
- skills/programmatic-seo/SKILL.mdSource checked 2026-09-08
- skills/ai-seo/evals/evals.jsonSource checked 2026-09-08
- tools/PARTNERS.mdSource checked 2026-09-08