菜单
Use when you need to model, measure, or improve the self-serve growth engine — to map the acquisition→activation→retention→referral loop, find the leakiest stage, and run one experiment against it.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when you need to assess whether a client account is healthy, at risk, or slipping — before renewal, after a rough patch, or on a regular cadence — and decide what to do about it.
Use when a client request is ready to become production work and you must brief creative or media — turning a vague ask into an objective, an audience, and constraints the team can build against.
Use when responding to an RFP or writing a new-business proposal — to decide whether to pursue it, shape the offer, and produce a document a client can say yes to.
Use when preparing the quarterly review a client account faces — to report results against the objective honestly, read what worked, and set what the next quarter buys.
Use when you need to write or change a statement of work — turning an agreed offer into a scope, deliverables, price, and terms that both protect the client and defend the agency's margin.
Use when reviewing compensation for a role, a team, or the whole population — checks where people sit against defensible bands, finds equity gaps, and produces a ranked, costed set of adjustments.
| name | product-led-growth-loop |
| description | Use when you need to model, measure, or improve the self-serve growth engine — to map the acquisition→activation→retention→referral loop, find the leakiest stage, and run one experiment against it. |
Product-led growth treats the product as the primary way users are acquired, activated, retained, and referred — a loop where each turn feeds the next, not a funnel that empties out the bottom. The whole discipline is: measure every stage, find the one that leaks worst, fix that one, re-baseline, repeat. Scattering effort across all stages at once is how you stay busy and flat.
Loop scorecard:
Acquisition → Signup: <rate>
Signup → Activation: <rate> <-- leakiest
Activation → Retention: <rate>
Retention → Referral: <rate>
Target stage: <stage> — because <diagnosis: messaging | friction | product>
Experiment: <hypothesis> | change: <one thing> | ship if <result>, kill if <result>
Result: <rate before → after> → <shipped | killed> → new target: <stage>