01
Recommended Skills CLI installation
The current README recommends npx skills add coreyhaines31/marketingskills. You can install the whole library, list available skills, or select only specific workflows.
- Install all with npx skills add coreyhaines31/marketingskills.
- Install selected skills with the --skill option.
- List the library before installing when you only need a narrow subset.
02
Claude Code and other install paths
When installation runs non-interactively inside an agent session, the CLI may target the universal .agents/skills directory. The current README documents explicitly targeting Claude Code with -a claude-code when that host-specific location is required.
- Claude Code also has a documented plugin installation route.
- Git clone and git submodule are useful when you want version-controlled source.
- SkillKit is documented as another multi-agent option.
03
Set up shared marketing context
The library expects useful product, audience and positioning context. The v2 layout centers that shared information on .agents/product-marketing.md so compatible hosts can reuse it.
- Populate real product facts before asking for downstream marketing work.
- Do not use a skill file as evidence for claims about your market.
- Keep client-specific or sensitive information within the appropriate project boundary.
04
Verify the installation safely
After installation, ask the agent to identify installed marketing skills and run a low-risk analysis. Confirm it is loading the intended skill and context instead of producing generic advice.
- If Claude Code cannot see a skill, inspect the install destination and use the documented explicit target.
- If old and new folders coexist, follow the v2 migration guide rather than deleting blindly.
- Keep publishing, outreach, ad and production changes human-reviewed until the workflow is trusted.
Sources
Primary and supporting sources
Facts were rechecked against the linked sources immediately before publication. Pricing, product availability and rollout status can change.