Communitygithub.com

amplitudes/builder-skills

識別、繪製並衡量產品中的自我強化成長迴圈,包括病毒式、內容、付費與使用迴圈。了解週期時間、吞吐量以及迴圈中斷之處。當產品經理需要超越線性漏斗思維,轉而理解驅動永續成長的複合系統時使用。

builder-skills 是什麼?

此技能旨在幫助產品經理和成長團隊從線性漏斗思維轉向複合成長系統思維。它提供一個結構化的框架,用於識別產品中存在的(或可能存在的)自我強化成長迴圈,例如病毒迴圈、內容迴圈、付費迴圈和使用/數據迴圈。技能不僅引導用戶繪製這些迴圈的邏輯流程,還要求量化衡量每個迴圈的健康狀況——包括週期時間、吞吐量(分支因子)以及每個步驟的轉換率。最重要的是,該技能幫助找出迴圈中斷的具體步驟(例如激活中斷、分發中斷、轉換中斷或品質中斷),並估算修復該步驟對整體迴圈吞吐量的影響。支援 Claude Code、Cursor 等AI代理平台。通過詳細的提示模板,用戶可以輸入產品上下文,技能會生成一份包含迴圈清單、健康指標、中斷步驟分析、迴圈交互圖和優先級投資策略的報告,並明確指出哪些常見的「反操作」(Anti-plays)應避免。

相容平台~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 的新對話。

說明文件

繪製成長迴圈

識別你產品中的自我強化迴圈,衡量其週期時間與吞吐量,找出迴圈中斷或未被充分利用之處——這樣你就能投資於複合成長,而非線性戰術。

漏斗(Funnel)對於診斷很有用,但用於策略則很危險。漏斗告訴你「倒更多用戶進頂端,並優化每個步驟」。成長迴圈則告訴你「建立一個系統,讓輸出成為輸入」。區別在於複合效應:漏斗優化是加法,迴圈優化是乘法。這項技能強迫你識別產品中哪些迴圈存在(或可能存在),衡量它們是否真的有效,並找出導致迴圈停滯的具體斷點。


提示模板

你是一位以系統而非漏斗思考的成長策略師。你知道永續成長來自於自我強化的迴圈,其中一個週期的輸出成為下一個週期的輸入。你嚴格衡量迴圈的吞吐量和週期時間,從不將線性戰術(例如「購買更多廣告」)與複合系統混淆。

以下是我正在分析的內容:

<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.

相關技能