Communitygithub.com

amplitud/builder-skills

将顶层指标分解为具有数学关系的量化指标树,对每个节点进行量化,并识别真正的杠杆点所在。当产品经理需要了解什么驱动指标、应该集中精力在哪里、以及不应该在哪里集中精力时使用。

builder-skills 是什么?

该技能帮助产品经理或增长负责人将顶层业务指标(如周活跃用户数)分解成一个结构化的、基于数学运算的指标树。它严格遵循五个步骤:1)建立指标层次(北极星指标、业务KPI、当前最重要的单一指标);2)通过明确的加法和乘法关系将指标分解2-3层,直到每个节点都可被单个团队拥有和直接影响;3)对树的每一个节点进行量化,拒绝未经量化的空想;4)评估每个指标的质量(可触达、可控、反馈快、可测试、可解释、不易作弊);5)基于量化树识别真正的杠杆节点和“反杠杆”节点(那些看似重要但实际收益很小的方向)。该技能特别强调“跟住体量”——优先在用户已经存在的地方寻找杠杆,而不是在没人使用的表面或流程上投入。适合在设定季度目标之前使用,帮助团队避免选择无法真正推动的指标。支持与实验设计技能配合使用,在识别杠杆后设计验证实验。建议每季度重新审视指标树,因为随着产品变化节点权重会转移。

兼容平台~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)。这必须与NSM结构上关联——如果NSM上升但业务KPI没有上升,则存在变现问题。
- **当前最重要的单一指标(OMTM):** 团队当前应专注的唯一战术指标。这将从树中浮现——它是杠杆最大的节点。

如果用户已经定义了这些指标,请确认它们。如果没有,请提出候选指标并解释权衡。

### 步骤2:分解为树结构

将NSM(或用户指定的任何顶层指标)分解为其组成部分。对于每个分支:

- **明确说明数学关系。** 使用加法(+)表示构成父指标的部分(例如MAU = 新用户 + 回访用户 + 召回用户)。使用乘法(x)表示基于比率的关系(例如新用户 = 应用商店浏览量 x 转化率)。
- **深入2-3层。** 当到达可由单个团队拥有并直接影响的指标时停止。
- **标记假设分支。** 如果关系是假设但未被证实的(例如“我们相信留存率由在首次会话内完成引导的用户驱动”),将其标记为需要验证的假设。明确区分这些与定义性分解。

以结构化文本格式呈现树,例如:

北极星指标:周活跃用户(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. 指标层次(北极星指标、业务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.

相关技能