菜单
Routes marketing tasks to the right skill and agent in the marketing team. Load when you need to market a product, grow traffic, write content, post on social, improve SEO, or engage a community — and you're not sure which marketing skill or agent to use.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Meta-skill that routes a task to the right engineering skill. Load this at the start of a session or when unsure which skill applies — it maps intent to the process that should govern the work.
Catches breaking changes between services before they ship, by testing the contract each consumer actually depends on instead of spinning up the whole system. Use when services deploy independently, when a provider API change could break a consumer, or when end-to-end integration tests are too slow and flaky to guard every service boundary.
Proves whether a change actually moves the metric, with a valid A/B test instead of a guess — a hypothesis, a primary metric, a pre-computed sample size, guardrail metrics, and an honest readout. Use when shipping a change meant to improve a number (conversion, retention, performance), running an A/B or holdout, or deciding whether a feature "worked."
Decouples deploy from release using feature flags — ship code dark, roll out gradually, kill instantly, and remove the flag once it's done. Use when releasing risky or large changes, rolling out by percentage/cohort, delivering A/B variants, or when stale flags are accumulating as debt.
Finds security risks at design time — before code exists — by mapping the system, enumerating how it could be attacked, and deciding what to do about each threat. Use when designing a feature that touches auth, data, money, or external input, when changing a trust boundary, or when a security-sensitive change needs a structured risk pass rather than a code-level review.
Designs durable, curated memory that an agent carries across sessions — what to persist, how to scope and retrieve it, and how to stop it from drifting or poisoning later runs. Use when an agent needs to remember decisions, preferences, or project facts beyond one context window, or when stale/over-generalized memory is corrupting its behavior.
基于 SOC 职业分类
| name | marketing-router |
| description | Routes marketing tasks to the right skill and agent in the marketing team. Load when you need to market a product, grow traffic, write content, post on social, improve SEO, or engage a community — and you're not sure which marketing skill or agent to use. |
The marketing team has eight skills and eight agents, grouped under skills/marketing/ and
agents/marketing/. This router maps your task to the right process — then load that skill's
SKILL.md and follow it fully ([[skill-router]] pattern for the Grow phase).
Skip when you already know the agent — go directly to prompts/agents/marketing/<agent>.md.
| You need to… | Load skill | Run agent |
|---|---|---|
| Plan GTM, positioning, channels, campaign calendar | [[growth-strategy]] | growth-lead |
| Write blog, tutorial, newsletter, landing copy | [[content-marketing]] | content-marketer |
| Post on X/LinkedIn/Reddit, launch threads | [[social-distribution]] | social-media-manager |
| Improve rankings, keywords, landing page SEO | [[seo-growth]] | seo-strategist |
| Build community, welcome flows, engagement | [[community-engagement]] | community-manager |
| Plan and run paid ads (Google, LinkedIn, Reddit) | [[paid-ads]] | paid-media-manager |
| Design email welcome / nurture sequences | [[email-nurture]] | email-marketer |
| Build referral / invite loops | [[referral-loop]] | referral-manager |
Skill files live at skills/marketing/<skill-name>/SKILL.md.
For a full launch, load [[launch-campaign]] — the Grow-phase conductor that runs this whole sequence with intake, sign-off, and the community-before-traffic ordering gate, and assembles the launch kit. Use the steps below directly only when running one phase in isolation.
Run in this order unless the campaign brief says otherwise:
growth-lead (strategy + briefs)
→ community-manager (seed before traffic)
→ seo-strategist (landing page + keywords)
→ content-marketer (launch blog + tutorials)
→ social-media-manager (post pack + launch thread)
→ growth-lead (weekly review)
Critical rule: community-manager seeds content before social-media-manager drives traffic.
| Skill | Reference checklist |
|---|---|
social-distribution | channel-checklist.md |
paid-ads | paid-ads-checklist.md |
email-nurture | email-nurture-checklist.md |
referral-loop | referral-loop-checklist.md |
content-marketing | content-checklist.md |
seo-growth | seo-checklist.md |
community-engagement | community-checklist.md |
growth-strategy | All of the above when reviewing channel feasibility |