菜单
Creates long-form marketing content that educates and converts — blog posts, tutorials, newsletters, case studies, and landing copy. Use when you need articles, guides, launch posts, or email content that drives developer engagement and sign-ups.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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.
| name | content-marketing |
| description | Creates long-form marketing content that educates and converts — blog posts, tutorials, newsletters, case studies, and landing copy. Use when you need articles, guides, launch posts, or email content that drives developer engagement and sign-ups. |
Developers trust useful content, not ad copy. This skill produces long-form pieces that teach something real, demonstrate the product honestly, and end with a clear next step. Content compounds — a good tutorial ranks for months; a generic promo dies in hours.
Chains from [[growth-strategy]] (brief, pillars, ICP) and feeds [[social-distribution]] (snippets), [[seo-growth]] (optimized pages), and [[community-engagement]] (discussion starters).
Skip for short social posts only — use [[social-distribution]] instead.
Load inputs from [[growth-strategy]] or gather:
If the topic doesn't serve the ICP or a message pillar, reject or reframe it.
Structure every piece:
Hook — specific pain or surprising stat (2–3 sentences)
Problem — why this matters to the reader
Insight — your angle (not generic advice)
Solution / walkthrough — steps, examples, screenshots placeholders
Product tie-in — natural, ≤20% of piece; show don't pitch
Proof — data, quote, mini case, or demo
CTA — one clear action
For tutorials: numbered steps, code/commands where relevant, expected outcome per step.
Rules:
[SCREENSHOT] or [GIF] placeholdersVoice: peer explaining something useful, not a brand shouting.
From one article, extract:
| Asset | Format | Channel |
|---|---|---|
| Thread | 5–8 tweets | X |
| Carousel outline | 5 slides | |
| Reddit post | Problem + link | Subreddit (value-first) |
| Newsletter blurb | 2 paragraphs | |
| Community question | Discussion prompt | Discord / forum |
List these in the deliverable even if another agent publishes them.
Self-check:
[VERIFY][VERIFY] tags left in published copyContent is done when: