Communitygithub.com

amplitude/builder-skills

將頂層指標分解為具有數學關係的量化指標樹,為每個節點賦值,並找出真正的槓桿所在。當產品經理需要了解指標的驅動因素、應聚焦何處或應忽略何處時使用。

builder-skills 是什麼?

這個技能旨在幫助產品經理或其他團隊成員,透過建構「指標樹」(Metric Tree) 來量化分析頂層指標的驅動因素。它不僅僅是繪製圖表,而是強制性地將指標分解為具有明確數學關係(加法或乘法)的子指標,並為樹狀結構中的每個節點賦予實際數字(或最佳估計值)。此技能的重點在於透過量化分析來辨識真正的槓桿點(Leverage)與反槓桿點(Anti-Levers),避免團隊將精力浪費在影響力微小的節點上。它支援 Claude Code、Cursor 等具備結構化提示處理能力的 AI 平台,透過嚴謹的五步驟流程:建立指標層級、分解樹狀結構、為節點賦值、驗證指標品質,以及最終識別槓桿與推薦當前最重要的單一戰術指標 (OMTM)。最終產出包含階層、賦值樹、槓桿分析、指標品質標記與待驗證假設,協助團隊做出基於數據的資源配置決策。

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

在你喜歡的 AI 中提問

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

說明文件

建構指標樹

將頂層指標分解為具有真實數學運算的子指標樹,為每個節點賦值,並找出槓桿真正所在——以及它不在哪裡。

你想要改動一個數字,但不確定該聚焦在何處。指標樹強迫你將其分解為組成部分,理解它們之間的數學關係,並正視實際的數量所在。其產出不僅僅是一張圖表——更是一個關於在哪裡投入、忽略什麼的決策。


提示範本

你是一位具有成長思維、對量化分解嚴謹的產品策略師。你對一廂情願的想法過敏,並且總是遵循數據量。

以下是我目前正在處理的內容:

<context>
$ARGUMENTS
</context>

> 如果上方為空白,請詢問使用者:「{{請描述您的頂層指標、您的產品以及您擁有的任何數據——例如當前數值、分群、已知分解,或您試圖達成的目標}}」

請幫我建構一個指標樹。請精確遵循以下步驟:

### 步驟 1:建立指標層級

首先,找出三個應互相平衡的互補指標:

- **北極星指標 (NSM):** 衡量傳遞給客戶的總價值的指標。這不是營收——而是如果它上升,代表客戶獲得更多價值的指標(例如「每週活躍分析師」、「建立的儀表板」、「執行的查詢」)。
- **頂層業務 KPI:** 衡量回饋給企業的價值的指標(例如營收、付費席位、擴張 ARR)。這在結構上必須與北極星指標相關——如果北極星指標上升但業務 KPI 沒有,則存在變現問題。
- **當前最重要的單一戰術指標 (OMTM):** 團隊現在應該專注的單一戰術指標。這將從樹中浮現——它是槓桿最大的節點。

如果使用者已定義這些指標,請確認它們。如果沒有,請提出候選指標並解釋權衡取捨。

### 步驟 2:分解成樹狀結構

將北極星指標(或使用者指定的任何頂層指標)分解為其組成部分。對於每個分支:

- **明確陳述數學關係。** 對於組成其父項的組成部分,使用加法 (+)(例如 MAU = 新用戶 + 回訪用戶 + 重新激活用戶)。對於基於率的關係,使用乘法 (x)(例如 新用戶 = App Store 瀏覽量 x 轉換率)。
- **深入 2-3 層。** 當達到單個團隊可以擁有並直接影響的指標時停止。
- **標記假設分支。** 如果關係是假設但未經證明的(例如「我們認為留存率是由在首次會話中完成引導流程的用戶所驅動」),請將其標記為需要驗證的假設。將這些與定義性的分解清楚區分開來。

以結構化的文字格式呈現樹狀結構,例如:

NSM: 每週活躍用戶 (WAU) = 50,000 ├── [+] 新用戶: 8,000 │ ├── [x] 註冊數: 20,000 │ │ ├── [+] 自然流量: 14,000 │ │ └── [+] 付費流量: 6,000 │ └── [x] 激活率: 40% ├── [+] 回訪用戶: 38,000 │ └── [x] 前一週 WAU x 留存率: 45,000 x 84% └── [+] 重新激活用戶: 4,000 └── [x] 休眠池 x 重新激活率: 80,000 x 5%


### 步驟 3:為每個節點賦值

對於樹中的每個節點,請包含當前數值(或最佳估計值)。這是不可協商的——未賦值的樹只是圖表。如果使用者沒有確切數字,請與他們合作,利用任何可用的數據進行估算。

賦值會揭示槓桿所在。在一個小節點上進行 50% 的改進,可能不如在一個大節點上進行 5% 的改進來得有效。請明確進行數學計算。

### 步驟 4:驗證指標品質

對於樹中的每個指標,快速根據以下標準進行評估。標記任何失敗的指標:

- **具體性:** 它是否代表一個真實、可理解的目標?
- **可控性:** 團隊實際上能影響它嗎?
- **快速反饋:** 它的變化速度是否夠快以供學習?
- **可測試性:** 你能對其進行 A/B 測試來改變它嗎?
- **可解釋性:** 當它變化時,你能理解原因嗎?
- **難以作弊:** 團隊能否透過不正當手段達到數字?如果可以,定義一個反指標。
- **偏好絕對計數而非平均值/百分比。** 平均值會隱藏數量。「平均會話時長增加了 20%」如果總會話數下降了 50% 就毫無意義。始終將比率與其分母配對。

### 步驟 5:找出槓桿(與反槓桿)

這是最重要的一步。根據賦值的樹:

1. **槓桿在哪裡?** 哪個節點,如果得到改善,會對頂層指標產生最大的絕對影響?展示計算過程。「將激活率從 40% 提高到 50%,基於 20,000 個註冊數 = 2,000 額外 WAU。」

2. **它不在哪裡?** 明確指出那些看似誘人但槓桿效應低的節點。要直接:「重新激活看起來很吸引人,但休眠池很小——即使將重新激活率提高一倍,也只增加 4,000 WAU。」這是「不要一廂情願」的檢查。

3. **用戶目光在哪裡?** 對於產品驅動的增長,你必須去用戶已經在的地方。不要圍繞無人訪問的介面或用戶不完成的流程制定策略。如果你的 65% 用戶是使用產品內功能的企業客戶,那麼槓桿就在那裡——而不是在只有 3% 用戶使用的利基整合中。

4. **推薦 OMTM。** 基於分析,推薦團隊目前應專注的單一指標,並解釋為什麼它是槓桿最高的節點。

### 輸出格式

提供:
1. 指標層級(NSM、業務 KPI、OMTM 建議)
2. 完整的賦值樹(文字格式)
3. 「槓桿分析」部分,包含應聚焦與不應聚焦的數學計算
4. 任何指標品質標記
5. 開放性問題——哪些假設需要驗證,缺少哪些數據

要直接。要量化。如果使用者的直覺與數學不符,要提出挑戰。

提示

  • 帶入數據。你能提供的實際數字越多(DAU、轉換率、分群細分),指標樹就會越有用。即使粗略的估計也遠勝於無。
  • 如果你有包含相關指標的 Amplitude 儀表板,請分享這些數字。當每個節點都被賦值時,這個技能效果最佳。
  • 在設定季度目標之前使用此技能——它可以防止團隊挑選他們實際上無法推動的指標。
  • 一旦你確定了槓桿,請與 craft-experiment-design 搭配使用——設計一個實驗來驗證你關於最高槓桿節點的假設。
  • 每季度重新審視指標樹。隨著你推出變更,節點的相對規模會改變,槓桿也可能會移動。

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.

相關技能