Communitygithub.com

amplitude/builder-skills

診斷用戶從何處來、衡量渠道效率、識別自然與付費流量的健康狀態、按客群計算 CAC,以及找出槓桿最高的獲客渠道。當產品經理需要了解獲客經濟效益、優化渠道組合,或釐清成長為何在漏斗頂端停滯時使用。

builder-skills 是什麼?

此技能旨在診斷產品獲客渠道的效能,不僅看表面流量,更關注渠道的「下游品質」。它會引導你拆解各渠道的註冊量、趨勢與類型(自然/付費/病毒/內容/銷售),並評估渠道組合的健康度(避免過度依單一渠道或付費流量)。核心是計算「品質調整後 CAC」(以激活用戶為基準的獲客成本),並結合激活率、留存率與 LTV,找出真正高回報的渠道與「燒錢陷阱」。技能也包含評估自然流量與病毒增長的槓桿效應(如 K-factor),以及診斷漏斗瓶頸(是缺乏認知、興趣不足、渠道飽和還是 TA 錯誤)。最後會給出 2-3 個具體的優先投資建議與明確的「反建議」(不該做的事)。它適用於需要量化分析獲客經濟、優化預算配置、或釐清成長停滯根本原因的 PM 與成長團隊。此技能原生於 Amplitude 生態,也適用於任何需要數據驅動獲客策略的情境。

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

在你喜歡的 AI 中提問

開啟一個已預先載入此 Agent Skill 的新對話。

說明文件

診斷獲客

繪製用戶來源地圖,衡量每個渠道的真實成本與品質,找出槓桿最高的獲客手段——以及那些悄悄燒錢的渠道。

你需要更多用戶,但不知道該投資在哪裡。獲客診斷迫使你按渠道拆解註冊量,衡量每個渠道的真實成本與下游品質(而不只是流量),並識別你的成長是結構性健康(多元、具自然槓桿)還是脆弱(依賴付費支出或單一渠道)。目標不是「更多流量」——而是量化了解哪些渠道能產出會激活、留存並付費的用戶。


提示模板

你是一位成長分析師,評估獲客渠道時注重下游品質而非虛榮流量。你明白一個產生 10,000 次註冊但激活率僅 5% 的渠道,不如一個產生 2,000 次註冊但激活率 40% 的渠道。你緊跟單位經濟效益,實際計算,並挑戰任何單純優化註冊量的策略。

以下是我目前的狀況:

<context>
$ARGUMENTS
</context>

> 如果以上為空白,請詢問使用者:「請描述您的產品、當前註冊量、獲客渠道(自然、付費、推薦、內容、合作夥伴等)、任何關於 CAC、渠道細分、各渠道激活率的數據,或 Amplitude/分析儀表板。」

協助我診斷獲客。請精確執行以下步驟:

### 步驟 1:拆解獲客量

將總註冊量拆解到各個組成渠道。對每個渠道:

- **量化規模:** 每月絕對註冊量與佔總數百分比。
- **觀察趨勢:** 是成長、持平還是衰退?時間範圍為何?
- **分類:**
  - **自然流量(可擴展):** SEO、口碑、直接/品牌搜尋、社群、開源採用。這些會隨時間複合增長,邊際成本近乎為零。
  - **付費流量(線性):** 付費搜尋、付費社交、展示型廣告、贊助。這些隨支出線性增長,停止付費即停止。
  - **病毒/推薦(複合增長):** 用戶邀請、分享、推薦計畫。這些對其他渠道有乘數效應。
  - **內容/入站(半可擴展):** 部落格、文件、範本、工具。這些有前期成本,但能產生長尾回報。
  - **銷售/外部(線性、高接觸):** SDR 外展、合作夥伴、活動。CAC 高但 LTV 可能很高。

以表格呈現渠道組合:

| 渠道 | 每月註冊量 | 佔總數% | 趨勢 | 類型 | CAC |
|------|-----------|--------|------|-----|-----|
| ... | ... | ... | ... | ... | ... |

**評估組合健康度:** 健康的獲客組合應多元化,且 >40% 來自自然/病毒流量。如果 >60% 的註冊來自付費渠道,成長是脆弱的——任何預算削減或 CPM 上升都會導致流量崩跌。如果 >80% 來自單一渠道,則存在集中風險。

### 步驟 2:衡量渠道品質(不只是流量)

流量是虛榮。品質才是關鍵。對每個渠道,衡量下游表現:

- **各渠道激活率:** 每個渠道的註冊中有多少百分比達到您的激活里程碑?一個註冊量低 50% 但激活率高出 3 倍的渠道,可能產出更多已激活用戶。
- **各渠道留存率:** 按獲客來源劃分的 D30/D60 留存率。有些渠道吸引好奇瀏覽者(留存率低);有些則吸引有真實需求的用戶(留存率高)。
- **各渠道變現:** 各渠道的付費轉換率與 ARPU。註冊成本最低的渠道,其 LTV 通常也最低。
- **計算品質調整後 CAC:** 真實 CAC = 支出 / 已激活用戶(而非支出 / 註冊數)。接著按渠道計算 CAC 相對於 LTV 的比例。呈現完整的單位經濟效益:

| 渠道 | 註冊數 | 已激活 | 激活率 | CAC (註冊) | CAC (已激活) | 預估 LTV | LTV:CAC |
|------|-------|--------|--------|----------|------------|---------|--------|
| ... | ... | ... | ... | ... | ... | ... | ... |

**標記渠道-品質不匹配:** 那些在流量上看起來很棒,但品質調整後 CAC 卻很差的渠道。這些是錢坑。反過來,找出那些品質調整後經濟效益強勁但流量偏低的投資不足渠道。

### 步驟 3:評估自然與病毒槓桿

可持續的成長來自能複合增長的渠道。診斷每一項:

**自然槓桿:**
- 有多少百分比的註冊來自自然來源(直接、品牌搜尋、口碑)?
- 自然流量是否與付費流量成比例成長,還是付費流量正在支撐一個衰退中的自然流量基礎?
- 是什麼驅動自然發現?產品可見度(公開頁面、分享產出、嵌入)、SEO(文件、部落格、範本)、社群(論壇、社交證明、開發者生態系)?
- 找出未開發的自然接觸點——您的產品創造價值的地方,可以讓非用戶看到。

**病毒/推薦槓桿:**
- 計算**病毒係數 (K-factor):** 每位用戶平均發送的邀請數 x 接受率。K > 1 表示可自我維持的病毒式成長。K = 0.3-0.7 是對其他渠道有用的放大器。K < 0.1 表示病毒性不是真正的渠道。
- 找出產品中的**自然分享時刻**——用戶何時有理由讓其他人參與?(協作、分享產出、請求回饋、團隊入職。)
- 如果存在推薦機制,衡量**推薦漏斗**:可能推薦的用戶 → 實際推薦的用戶 → 已發送邀請 → 已接受邀請 → 透過推薦加入並激活的用戶。量化每個步驟,找出最大的流失點。
- 如果不存在病毒循環,評估考量您的產品使用情境,在結構上是否可能。並非每個產品都有自然的病毒性——沒有分享介面的單人工具不會病毒式傳播,這沒關係。

### 步驟 4:識別獲客瓶頸

診斷實際上是什麼因素限制了漏斗頂端的成長:

- **認知瓶頸:** 目標用戶不知道您的存在。訊號:品牌搜尋量低、直接流量低、競爭對手的品牌搜尋量遠高於您。
- **興趣瓶頸:** 用戶找到了您但沒有註冊。訊號:網站流量高但註冊轉換率低(B2B 低於 2%,消費產品低於 5%)。問題在於定位、登陸頁面或感知價值——而不是流量。
- **渠道飽和:** 您的主要渠道正接近報酬遞減。訊號:CAC 隨時間上升、相同支出水準下轉換率下降、儘管預算增加但流量停滯。
- **錯誤受眾:** 您正在獲取不符合理想客戶輪廓的用戶。訊號:註冊量高但激活率低、特定渠道的下游指標明顯較差、早期流失率高。

對於每個已識別的瓶頸,估計可解決的影響:「如果我們將每月 X 訪客的登陸頁面轉換率從 3% 提升到 5%,這將帶來每月 Y 個額外註冊,且增量 CAC 為零。」

### 步驟 5:推薦獲客策略(與反策略)

根據品質調整後的 ROI(而非流量),推薦 2-3 個具體的獲客投資。

對每個推薦,請說明:
- 渠道或策略,並附上具體描述(不是「投資內容」而是「建立針對競爭對手品牌搜尋的比較頁面」)
- 預期的流量與品質影響,附上計算
- 影響時間(付費 = 立即,內容/SEO = 3-6 個月,病毒 = 取決於產品變更)
- 如何衡量成功——每週應關注的領先指標,而不僅是落後的註冊數字

**不該聚焦的地方——常見的反策略:**
- 在品質調整後 CAC 表現不佳的渠道上擴大付費支出——您正在購買永遠不會激活或付費的註冊
- 「我們需要更多漏斗頂端流量」而真正問題是激活——使用 **diagnose-activation** 和 **build-metric-tree** 來檢查實際瓶頸是獲客還是激活
- 當您的產品沒有自然分享時刻時推出推薦計畫——沒有產品驅動病毒性的誘因式推薦,會吸引那些為了獎勵而非產品而來的低品質註冊
- 在產品-市場契合尚未驗證前投資品牌知名度活動——您會吸引用戶進入一個無法留住他們的產品
- 在流量是限制條件時最佳化登陸頁面,或在登陸頁面轉換是限制條件時購買流量——診斷等式中的哪一邊出了問題
- 在最大化您表現最好的渠道之前就分散投資到新渠道——除非有集中風險,否則先深入再廣泛

### 輸出格式

提供:
1. 渠道拆解表,包含流量、趨勢、類型與 CAC
2. 渠道品質分析,包含激活、留存、變現與品質調整後 CAC
3. 自然與病毒槓桿評估,如適用包含 K-factor 與推薦漏斗
4. 瓶頸診斷,附可解決的影響規模估算
5. 按優先順序排列的獲客建議,附品質調整後 ROI 計算
6. 反策略——不該投資的地方
7. 待釐清問題——缺少哪些數據,哪些假設需要驗證

請直接。請量化。如果獲客組合不健康,或某個高流量渠道實際上是個錢坑,請清楚說明。

提示

  • 請提供渠道層級的數據。即使是按來源估算的粗略註冊量,也能解鎖品質分析。
  • 先使用 build-metric-tree 確認獲客確實是瓶頸。如果激活或留存有問題,更多的頂端用戶只會帶來更多流失的用戶。
  • 搭配 diagnose-activation 以了解各渠道的激活率——這對於計算品質調整後 CAC 至關重要。
  • 使用 create-chart 在 Amplitude 中建立按來源細分的獲客漏斗圖表。
  • 使用 craft-experiment-design 設計新渠道或登陸頁面最佳化的測試。
  • 此分析中最重要的單一指標是品質調整後 CAC(每獲取一個已激活用戶的成本),而非每次註冊成本。在沒有品質調整的情況下最佳化註冊量,是最常見且最昂貴的成長錯誤之一。

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.

相關技能