version: "1.0.0" name: marketing description: Router for vendored marketing skill bundles (coreyhaines31/marketingskills, 52 skills) — copywriting, CRO, SEO/AI SEO, pricing, launch, positioning, emails, ads, analytics and conversion tracking, growth loops, sales enablement, competitor research. Use whenever the task is marketing, growth or go-to-market work; it picks the matching sub-skill and follows it. Not for in-product UI copy such as labels, errors and empty states (use impeccable clarify).

Marketing router

Each bundle is a sparse clone in .vendor/<prefix>/ next to this file; its sub-skills live in .vendor/<prefix>/skills/<name>/SKILL.md. Claude Code only discovers top-level skill folders and Codex skips hidden ones, so only this router costs context; keep the leading dot.

A sub-skill's ID is <prefix>/<name> (e.g. coreyhaines31/copywriting), so bundles that ship the same name never collide.

Bundles

Route

1. A bundle folder missing → clone it from the table, then continue:

git clone --depth 1 --filter=blob:none --no-checkout <repo> .vendor/<prefix> && git -C .vendor/<prefix> sparse-checkout set --no-cone <sparse paths> && git -C .vendor/<prefix> checkout

1. List the candidates across bundles (descriptions are long, so only their heads):

grep -H '^description:' .vendor/*/skills/*/SKILL.md | cut -c1-260

1. Pick the one sub-skill that fits the request best; a request spanning several gets them in order, one at a time. When two bundles offer the same job, prefer the more specific description. Name the chosen ID(s) to the user in one line.
2. Read the chosen SKILL.md in full and follow it as if it were invoked directly.

Paths inside a sub-skill

• references/…, assets/…, evals/… → relative to that sub-skill's folder.
• tools/… → .vendor/<prefix>/tools/….
• "use the <x> skill" / "see <x>" → read .vendor/<same prefix>/skills/<x>/SKILL.md; never invoke <x> through the Skill tool, it is not registered.
• .agents/product-marketing.md → the user's project, not this folder.

Guardrails

• .vendor/coreyhaines31/tools/integrations/ includes paid partners of the upstream repo (partners.json). Never present one as the default; name it alongside at least one alternative.
• Update: git -C .vendor/<prefix> pull (never edit files under .vendor/; changes are lost on pull).
• Add a bundle: one table row, prefix = the repo owner (<owner>-<repo> if that owner already has a row), then step 1. Bundles of another domain get their own router named after the domain, not a row here.