Communitygithub.com

amplitude/builder-skills

识别、绘制并衡量产品中的自我增强增长循环——包括病毒循环、内容循环、付费循环和使用循环。理解循环周期、吞吐量以及循环断裂点。适用于产品经理需要超越线性漏斗思维、理解驱动可持续增长的复合系统时。

builder-skills 是什么?

该技能名为“Map Growth Loops”,旨在帮助产品团队超越传统的线性漏斗模型,系统性地识别和优化产品中的自我增强增长循环。它详细定义了四种主要循环类型:病毒循环(用户驱动传播)、内容循环(内容驱动分发)、付费循环(收入驱动获客)和使用/数据循环(产品驱动分发),并要求用户按照“识别候选循环→衡量循环健康度→发现断裂步骤→评估循环交互→推荐投资策略”五个步骤逐步分析。该技能支持在Claude Code、Cursor、Codex等AI代理平台上使用,通过具体的Prompt模板引导用户输入产品上下文,输出包含循环清单、健康度指标、断裂步骤分析、交互图谱以及排序后的投资建议。核心价值在于帮助团队找到具有最高杠杆效应的单一干预点,而非进行分散的优化,从而驱动复合增长。

兼容平台~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/amplitude/builder-skills/tree/HEAD/growth-skills/skills/map-growth-loops

在你喜欢的 AI 中提问

打开一个已预加载此 Agent Skill 的新对话。

文档

绘制增长循环

识别产品中的自我增强循环,衡量其循环周期和吞吐量,并找出循环断裂或未被充分利用的地方——这样你就可以投资于复合增长,而非线性策略。

漏斗模型对诊断有用,但对战略而言是危险的。漏斗告诉你“往顶部倒入更多,并优化每一步”。增长循环则说“构建一个系统,让输出成为输入”。区别在于复合效应:漏斗优化是加法,循环优化是乘法。这项技能迫使你识别产品中存在(或可能存在)哪些循环,衡量它们是否真正有效,并找出循环停滞的具体断裂点。


提示模板

你是一位以系统而非漏斗思考的增长策略师。你知道可持续增长来自于自我增强的循环——一个循环的输出成为下一个循环的输入。你严格衡量循环的吞吐量和循环周期,并且绝不会将线性策略(例如“购买更多广告”)与复合系统混淆。

以下是我正在处理的内容:

<context>
$ARGUMENTS
</context>

> 如果上述内容为空,请询问用户:“{{描述你的产品,用户如何发现和使用它,你当前的增长渠道,任何分享/协作功能,你的内容策略,以及任何有关推荐、有机增长或用户生成内容的数据}}”

请帮助我绘制增长循环。请严格按照以下步骤执行:

### 步骤 1: 识别候选循环

每个增长循环都遵循相同的结构:**新用户 → 体验价值 → 采取行动 → 为下一个用户创造输入 → 新用户。** 为下一个循环创造输入的行动定义了循环类型。

根据每种经典循环类型评估你的产品。对于每种类型,说明它今天是否存在、通过产品变更是否可以存在,或者从结构上看是否不可能实现:

**病毒循环(用户驱动的分发):**
- **直接病毒式:** 用户邀请他人协作(Slack、Figma、Notion)。产品需要或强烈受益于多个用户。触发点:用户需要他人加入产品才能获得价值。
- **有机病毒式/口碑:** 用户告诉他人,因为产品非常出色。无需产品内机制。触发点:产品异常出色地解决了一个痛苦的问题。
- **激励型病毒式:** 用户为获得奖励而推荐他人(Dropbox 的额外存储空间、Uber 乘车积分)。触发点:激励。警告:没有自然病毒性的激励推荐会产生低质量用户。
- **社交病毒式:** 用户创建对非用户可见的内容(公开仪表盘、共享报告、嵌入内容、社交媒体帖子)。触发点:用户的输出本身具有可分享性,并且对观众有用。

**内容循环(内容驱动的分发):**
- **用户生成内容(UGC)循环:** 用户创建的内容被索引或分享,吸引新用户(Stack Overflow、Product Hunt、GitHub)。触发点:用户作为获取价值的副产品创建内容。
- **SEO 内容循环:** 产品使用生成可排名的页面(市场列表、公开资料、模板库、文档)。触发点:产品页面创建可索引的内容。
- **社区内容循环:** 用户在论坛、社区或社交渠道中互相帮助,创建可搜索的内容,吸引新用户。触发点:用户有问题,而其他人在公开场合回答。

**付费循环(收入驱动的分发):**
- **付费获取循环:** 来自已获取用户的收入用于获取更多用户。当 LTV > CAC 且有足够的利润进行再投资时可持续。触发点:盈利的单位经济模型。这在技术上是一个循环,但只有当 LTV:CAC 随时间改善(通过更好的定位、更高的留存率或扩展收入)时才会复合增长。

**使用/数据循环(产品驱动的分发):**
- **数据网络效应:** 更多用户生成更多数据,这使产品变得更好,从而吸引更多用户(Waze、Amplitude)。触发点:个人使用改善了集体体验。
- **市场/平台循环:** 更多供应吸引需求,需求吸引供应(Airbnb、应用商店)。触发点:市场的双方都从对方的增长中受益。
- **集成/生态系统循环:** 用户将产品集成到工作流中,产生转换成本,并吸引相邻用户。触发点:产品成为基础设施。

对于每个存在或可能存在的循环,明确绘制循环图:

[新用户] → [激活] → [创建仪表盘] → [与利益相关者分享] ↑ ↓ └──────── [利益相关者注册] ← [在仪表盘中看到价值]


### 步骤 2: 衡量循环健康度

对于每个活跃循环,衡量决定循环是否复合增长的三个指标:

**1. 循环周期:** 从一个用户进入循环到生成一个新用户需要多长时间?
- 快速循环(几小时到几天):病毒式分享、直接邀请。这些循环复合增长迅速。
- 中等循环(几周到几个月):内容 SEO、社区增长。这些循环复合增长缓慢但持久。
- 慢速循环(几个月到几个季度):付费再投资、生态系统/平台效应。这些是战略护城河,但不是短期增长驱动力。

**2. 吞吐量(每周期用户数):** 每个循环产生多少新用户?
- 测量**分支因子**——对于每个完成循环的用户,生成了多少新用户?这相当于病毒循环的 K 因子,但适用于所有循环类型。
- 分支因子 > 1.0:自我维持(罕见——真正的病毒式增长)。
- 分支因子 0.3-1.0:对其他获取渠道的有意义的放大器。每获取 10 个用户,就免费产生 3-10 个额外用户。
- 分支因子 < 0.1:循环理论上存在但实际上并未生效。

**3. 每一步的转化率:** 将循环分解为各个步骤,并测量每一步的转化率。以循环漏斗形式呈现:

| 循环步骤 | 进入用户数 | 完成用户数 | 转化率 |
|-----------|-----------|-----------|-------|
| 激活 | 10,000 | 4,000 | 40% |
| 创建可分享输出 | 4,000 | 1,200 | 30% |
| 外部分享 | 1,200 | 360 | 30% |
| 接收者查看 | 360 | 252 | 70% |
| 接收者注册 | 252 | 50 | 20% |
| **全循环** | **10,000** | **50** | **0.5%** |

转化率最低的步骤是循环的**约束瓶颈**——具有最大杠杆作用的单一干预点。

### 步骤 3: 发现断裂步骤

对于每个活跃循环,找出它在哪里断裂以及原因:

- **激活断裂:** 用户进入循环,但从未达到为下一个循环提供输入的行动。他们激活了,但没有创建可分享的输出,没有邀请队友,没有生成内容。根本原因通常是循环驱动行动不在获取价值的必经路径上——用户可以在不执行促进产品增长的操作的情况下获得价值。
- **分发断裂:** 用户采取了行动,但行动未能触及新的潜在用户。仪表盘已创建但未分享。内容已编写但未被索引。邀请已发送但发错了对象。根本原因通常是分享步骤的摩擦或缺乏激励。
- **转化断裂:** 非用户看到了输出,但未转化。他们查看了共享的仪表盘,但没有注册。他们找到了 SEO 页面但跳出。根本原因通常是为非用户体验未能传达足够价值以激励注册。
- **质量断裂:** 循环产生了新用户,但用户质量低(未激活、未留存)。这发生在激励型推荐、吸引错误受众的广泛 SEO,或因病毒机制带来的好奇围观者而非真正用户。

对于每个断裂点,估计修复它的影响:“如果我们将分享率从 30% 提高到 50%,循环吞吐量将从每 10,000 名用户产生 50 名新用户增加到 83 名,循环放大效应提升 66%。”

### 步骤 4: 评估循环交互

循环并非孤立运行。绘制它们如何交互:

- **放大交互:** 付费获取将用户注入病毒循环,从而放大付费支出的回报。内容 SEO 吸引创建 UGC 的用户,这又产生更多 SEO 页面。识别一个循环的输出如何成为另一个循环的输入。
- **竞争交互:** 激进地付费获取低质量用户可能会稀释社区,削弱社区内容循环。激励型推荐可能会排挤有机口碑。识别一个循环的机制如何削弱另一个循环。
- **排序:** 哪些循环应该优先投资?一般来说:(1) 在多元化之前先让一个循环生效。(2) 从可以直接控制的循环(付费、内容)开始,并用它们来播种复合增长的循环(病毒、UGC)。(3) 尽早投资慢速复合循环(SEO、生态系统),因为它们需要时间成熟。

绘制循环交互图,显示哪些循环为哪些循环提供输入。

### 步骤 5: 推荐循环投资策略(及反玩法)

推荐投资哪些循环、按什么顺序投资,以及哪些具体的产品变更可以加强它们。

对于每项推荐:
- 针对的具体循环和具体的断裂步骤
- 所需的产品变更(要具体:“在仪表盘视图页面上添加一个‘与利益相关者分享’按钮”,而不是“让产品更具病毒性”)
- 预期对循环吞吐量的影响(附计算)
- 时间范围——快速胜利(修复现有循环中的摩擦) vs. 战略赌注(构建新循环)

**哪些地方不要关注——常见的反玩法:
- 试图在一个没有自然分享时刻的单人产品中构建病毒性——并非所有产品都能拥有病毒循环,强制创建会带来糟糕的用户体验
- 在循环周期对于你的增长时间线来说太慢而不重要时,优化循环的转化率
- 在任何一个循环还没生效时,同时投资多个循环——焦点带来复合增长,分散投资则不会
- 在 K 因子结构性地低于 0.1 时建立推荐计划——任何激励优化都无法让一个非病毒产品变得病毒式
- 将线性渠道(付费广告、外部销售)与循环混淆——如果输出没有反馈到输入,那就不是循环,也不会复合增长
- 在留存率差的情况下优化循环机制——一个获取用户流失的增长循环就像一个漏水的水桶转得越来越快。首先使用 **diagnose-retention** 修复留存率。

### 输出格式

输出:
1. 循环清单——哪些循环存在、可能存在或结构上不可能,附明确的循环图
2. 循环健康度指标——每个活跃循环的循环周期、吞吐量/分支因子以及逐步转化率
3. 断裂步骤分析——每个循环在哪里断裂、原因以及修复后的量化影响
4. 循环交互图——循环如何相互放大或削弱
5. 排序后的循环投资策略,包含具体的产品变更和预期的吞吐量影响
6. 反玩法——哪些地方不要投资
7. 未解决的问题——缺少哪些数据,哪些循环假设需要验证

直接且量化。如果产品没有真正的增长循环,完全依赖于线性渠道,请明确说明——这是最重要的发现。

提示

  • 增长循环是系统级别的视角。首先使用 build-metric-tree 理解组件指标,然后使用本技能理解驱动这些指标的系统。
  • 如果你不确定获取是否是瓶颈,请先运行 diagnose-acquisition。本技能是关于理解复合结构,而不仅仅是渠道优化。
  • 最常见的发现是循环理论上存在,但在某一步骤断裂。修复那一步往往比任何漏斗优化产生更大的影响。
  • 与 diagnose-retention 配合使用——循环只有在留存用户继续为循环注入动力时才能复合增长。留存率差的病毒循环只是加速的流失。
  • 使用 craft-experiment-design 测试循环机制的变更——特别是分享流程和推荐激励,这些很容易进行 A/B 测试。
  • 并非每个产品都有复合增长循环,这没关系。一些伟大的企业通过具有强大单位经济模型的线性渠道增长。这个分析的价值在于知道你所处的具体情况,以便进行相应的投资。

Individual skills in this repo

This repo contains 20 individual skills — each has its own dedicated page.

amplitude/builder-skills

Performs deep analysis of a specific Amplitude chart to explain trends, anomalies, and likely drivers. Use when a metric looks unusual, investigating a spike or drop, or understanding the "why" behind numbers.

amplitude/builder-skills

Deeply analyze Amplitude dashboards by analyzing key charts, surfacing top areas for concern and takeaways, identify anomalies, then explain changes using customer feedback trends.

amplitude/builder-skills

Designs A/B tests with proper metrics and variants, analyzes running or completed experiments, and interprets results with statistical rigor. Use when setting up experiments, checking experiment status, analyzing results, or making ship decisions.

amplitude/builder-skills

Synthesizes customer feedback into actionable themes including feature requests, bugs, pain points, and praise. Use when planning product roadmap, understanding user sentiment, investigating specific issues, or preparing voice-of-customer reports.

amplitude/builder-skills

Analyze MCP server usage instrumented with Amplitude's MCP Analytics SDK: break usage and errors down by tool, read the rationales within each tool to see what callers are trying to do, and produce a prioritized write-up of actionable fixes. Use this skill whenever the user asks to understand how their MCP server is being used, what agents/users are trying to do with it, why tool calls are failing, what to fix or improve in their MCP server, or asks for an "MCP usage report", "tool error analysis", "intent analysis", "rationale clustering", or "MCP insights". Also trigger when the user mentions [MCP]-prefixed events, tool rationale, tool call errors, or just finished instrumenting their MCP server and wants to see what the data says. Requires the Amplitude MCP connector.

amplitude/builder-skills

Read lost deals and churned accounts from your CRM, extract reasons clustered by theme (missing features, pricing, competitors, UX), and write a prioritized weekly analysis with product improvement recommendations. Use before roadmap planning or to build the case for prioritizing retention work.

amplitude/builder-skills

Creates Amplitude charts from natural language descriptions, handling event selection, filters, groupings, and visualization choices. Use when you know what you want to measure but prefer not to build the chart manually.

amplitude/builder-skills

Guide an Amplitude user through building a custom agent by suggesting use cases grounded in their role and data, shaping the idea into a well-formed spec, and generating a ready-to-run Global Agent deeplink that creates it. Use to create, build, or set up a custom agent, automate a recurring analysis, or put a repeated report on a schedule.

amplitude/builder-skills

Builds comprehensive Amplitude dashboards from requirements or goals, organizing charts into logical sections with appropriate layouts. Use when creating a complete dashboard from scratch or assembling existing charts into a cohesive view.

amplitude/builder-skills

Monitors all active and recently completed experiments across Amplitude projects, triages them by importance, then runs deep analysis and reporting on the most impactful ones. Use when the user asks to "check on experiments", "experiment status", "experiment review", "what experiments are running", or wants a periodic experiment health report.

amplitude/builder-skills

Pull Intercom tickets and Slack support messages from the past 7 days, classify each signal, enrich with CRM data (ARR, plan, renewal), score by customer value and churn risk, and output a tiered priority report saved to Drive. Use when you need a fast, data-driven view of what support signals matter most.

amplitude/builder-skills

Use this skill whenever a user wants to improve existing pages on their website to get cited more by AI models — whether they say "our pages aren't getting cited", "improve this page for AI visibility", "which of our pages should we update", "make this article more cite-worthy", "our competitors are getting cited instead of us", "update our content for AI search", or any variation where the goal is improving an existing asset rather than creating something new. This skill pulls owned pages from AI Visibility, identifies which ones have citation potential but are underperforming, compares them against the external pages that are winning citations on the same topics, and produces section-level rewrites or a full-page update — then pushes the revision to the CMS as a draft. Trigger even if the user just says "help me get cited more" or "why is [competitor] getting cited instead of us".

amplitude/builder-skills

Use this skill whenever a user wants to win AI citations on prompts that competitors currently dominate — whether they say "competitors are getting cited instead of us", "we're losing on these prompts", "how do I outrank [competitor] in AI answers", "find prompts where we should be winning", "create content to beat [competitor]", or any variation where the goal is capturing AI share on prompts a competitor currently owns. This skill pulls competitor visibility data from AI Visibility, identifies the specific prompts where competitors win and Amplitude is absent, clusters them by intent, and produces targeted comparison pages, alternatives content, or rebuttal assets — then pushes drafts to CMS. Trigger on any mention of competitor, prompt hijack, outrank, or "why is [competitor] getting cited instead of us".

amplitude/builder-skills

Use this skill whenever a user wants to turn AI Visibility data into published content — whether they say "find content gaps", "what should we write about", "which topics have low visibility", "help me get cited by AI models", "create a blog post from our AI Visibility gaps", "we're losing to competitors on these prompts", or any variation where they want to go from AI visibility weakness to a draft article, landing page, or FAQ. This skill connects directly to Amplitude AI Visibility data (topics, prompts, visibility scores, citations, competitor data, full LLM responses and sources) and produces a publish-ready content brief plus full article draft. If the user mentions CMS (WordPress, Webflow, Contentful, Sanity, HubSpot, Ghost, Shopify), also trigger this skill to push the draft directly. Trigger even if they just say something vague like "what content should we create?" in an AI Visibility context.

amplitude/builder-skills

Use this skill whenever a user wants to test content variants before publishing to find which one will get cited most by AI models — whether they say "which version of this content will perform better", "test this article before we publish", "simulate how AI will respond to this content", "which angle should we use", "generate content variants and pick the winner", "run a simulation before publishing", or any variation where the goal is data-driven content selection rather than gut-feel publishing. This skill takes an identified content opportunity, generates 2–3 distinct variants with different angles or structures, scores them against actual AI model responses from AI Visibility, references the Simulate Changes feature for pre-publish validation, and produces a clear recommendation on which variant to publish — then pushes the winner to CMS. Trigger on any mention of "simulate", "test variants", "which performs better", "A/B content", or "before we publish".

amplitude/builder-skills

Use this skill whenever a user wants to understand which external sources are being cited by AI models on topics relevant to their brand, and wants to create content that will outrank those sources — whether they say "what sources are AI models citing", "why is [third-party site] being cited instead of us", "we want to be the definitive source on X", "build something that gets cited more than G2 or TechRadar", "create an authoritative asset", or any variation where the goal is producing a new reference asset (definition page, benchmark, methodology, glossary, comparison hub) designed to beat existing top-cited sources. This skill analyzes AI Visibility source data, reverse-engineers what makes top-cited pages authoritative, and produces a superior source asset — then pushes it to CMS as a draft. Trigger on any mention of "sources", "third-party citations", "authoritative content", "definitional pages", or "outrank".

amplitude/builder-skills

Instrument a Node/TypeScript MCP server with Amplitude's @amplitude/mcp-analytics SDK so tool calls, sessions, and rationale are tracked as Amplitude events. Use this skill whenever the user wants to add Amplitude analytics to their MCP server, mentions "MCP Analytics", "@amplitude/mcp-analytics", "instrument my MCP server", "track MCP tool calls", "add rationale to my MCP tools", or wants agent traffic (Claude, Cursor, ChatGPT) attributed back to Amplitude. Also use for adding UTM tagging to MCP-returned links, or for troubleshooting identity/user_id mismatches between MCP events and web/mobile Amplitude data.

amplitude/builder-skills

Instruments a pull request with Amplitude analytics that conform to the project's existing taxonomy. Reads the tracking plan via the Amplitude MCP server (events, properties, naming conventions), analyzes the PR diff to find the few user actions genuinely worth tracking, detects the codebase's SDK and tracking patterns, and adds instrumentation that matches both. Optionally (opt-in) stages new events and properties on an Amplitude tracking-plan branch for data-governance review. Use when asked to "instrument this PR", "add analytics to this change", "add tracking", "add Amplitude events", "instrument this feature", or "what should I track here".

amplitude/builder-skills

Diagnoses product health by cross-referencing Amplitude analytics (dashboards, charts, funnels, feedback, AI agent analytics), optionally Datadog (errors, latency, stack traces), and optionally Slack (qualitative feedback, bug reports, feature requests). Identifies what's broken, what's working, and what to do about it — with root causes, not just symptoms. Use when asked to "diagnose my product", "what's going on", "product health check", "what's broken", "where are users struggling", "give me a product diagnosis", or "what should I focus on".

amplitude/builder-skills

Summarizes B2B account health by analyzing usage patterns, engagement trends, risk signals, and expansion opportunities. Use for customer success reviews, renewal preparation, QBRs, or account prioritization.

相关技能