Communitygithub.com

amplitude/builder-skills

定义一个北极星指标及其输入指标。对产品所玩的游戏进行分类,根据质量标准评估候选指标,并构建一个关联的指标体系。用于选择北极星指标、评估现有指标或建立指标框架时。

builder-skills 是什么?

该技能帮助产品团队定义并实施北极星指标(North Star Metric, NSM),这是最能反映客户从产品中获得价值的单一指标。它指导用户完成六个关键步骤:对产品所玩的游戏(注意力、交易或生产力)进行分类,生成并评估NSM候选指标,推荐最佳指标,定义3-5个驱动性输入指标,并验证整个指标系统。技能强调NSM应预测收入,而非等同于收入或日活跃用户等虚荣指标。支持Amplitude平台,通过提示驱动的方式,利用用户提供的产品背景(如产品描述、客户细分和商业模式)生成有针对性的建议。输出包括游戏分类、评估分数、输入指标及所有权分配、系统验证和后续步骤。该技能特别适合产品经理、增长负责人和数据分析师,用于将团队围绕真正的客户价值进行对齐,并建立可衡量的业务增长框架。

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

在你喜欢的 AI 中提问

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

文档

北极星指标

定义一个能够捕捉客户价值、协调团队、并预测长期业务成功的北极星指标。

北极星指标不仅仅是“你追踪的数字”。它是唯一最能反映客户从你的产品中获得价值的指标。做对了,它能协调产品、工程、营销和领导层关注真正重要的事情。做错了,团队就会优化那些在演示文稿中很好看,但不会推动业务的虚荣指标。


领域背景

北极星指标是什么

北极星指标(NSM)是一个单一的、以客户为中心的度量,反映了人们从你的产品中获得的总体价值。它有三个作用:

  1. 清晰与对齐 — 定义产品团队优化的内容以及可以接受的权衡
  2. 沟通 — 向利益相关者展示产品组织的影响和进展
  3. 问责 — 让团队对结果负责,而不仅仅是交付功能

北极星指标不是什么

  • 不是收入。 收入是滞后指标。当你统计它时,已经无法影响结果了。你的NSM应该预测收入,而不是成为收入。
  • 不是日活跃用户或注册用户。 这些是虚荣指标——表面上看起来很好,但无法告诉你客户是否获得了价值。
  • 不是OKR。 OKR是目标设定工具。你可以用关键结果来表达NSM的预期变化,但它们是不同的东西。
  • 不是一个以上的指标。 每条产品线只有一个NSM。如果有相互竞争的北极星,那你就没有北极星。

三类游戏

在选择NSM之前,先确定你的产品玩的是哪类游戏:

  • 注意力游戏 — 成功 = 用户在产品的使用时长。用户为了内容、娱乐或持续互动而来。(例如:Netflix, Spotify, TikTok)
  • 交易游戏 — 成功 = 交易量。用户为了购买、销售或交换价值而来。(例如:Amazon, Airbnb, Stripe)
  • 生产力游戏 — 成功 = 高效完成工作。用户为了更快或更好地完成工作而来。(例如:Notion, Figma, Amplitude)

大多数产品只玩一类游戏。试图同时玩三类游戏会分散焦点。在选择指标前,先了解你的游戏。

指标体系:NSM + 输入指标 + 业务关键绩效指标

北极星不能单独运作。你需要三个层面:

  1. 北极星指标 — 总体客户价值(例如,教育产品的“每周学习时长”)
  2. 输入指标(3-5个) — 可控制的、互补的驱动因素,推动NSM。一个有用的模式是:广度(多少客户?)、深度(每个客户多少价值?)、频率(多久一次?)、效率(多快速/多无摩擦?)。这些是团队日常真正推动的指标。
  3. 顶层业务关键绩效指标 — 回馈给业务的价值(收入、付费席位、年经常性收入)。这必须在结构上与NSM相关联。如果NSM上升但业务关键绩效指标没有,那么你的变现有问题。如果业务关键绩效指标上升但NSM没有,那么你是在榨取你没有创造的价值。

何时使用

  • 定义或重新定义产品的关键指标
  • 评估你当前的北极星是否真的很好
  • 为新产品或团队建立指标框架
  • 协调利益相关者对成功的定义
  • 为规划季或OKR设定做准备

提示

你是一位专门研究北极星指标和增长衡量框架的产品战略家。你深入了解Amplitude北极星框架,并帮助团队超越虚荣指标,找到真正捕捉客户价值的指标。

根据以下关于我产品的背景信息:$ARGUMENTS

按照以下步骤进行:

步骤1:对游戏进行分类

确定该产品玩的是哪类游戏:注意力、交易 或 生产力。解释你的推理。如果产品跨越两类游戏,确定主要类别并解释为什么聚焦很重要。

步骤2:生成NSM候选指标

提出2-3个北极星指标候选。对于每个候选指标:

  • 清晰说明指标(名称 + 单位 + 时间窗口)
  • 解释它捕捉了什么客户价值
  • 解释为什么它是业务成功的先行指标

同时提出1-2个故意选差的候选指标,并解释它们为什么失败。这有助于厘清好的NSM的标准——有时看清错误比看清正确更容易。

步骤3:根据质量标准进行评估

根据以下六个标准对每个候选指标进行评分:

  1. 客户价值 — 它是否反映了客户获得的价值,而不仅仅是活动?增加这个指标是否真的意味着客户情况更好?
  2. 战略清晰度 — 有人看到这个指标就能理解你的产品策略吗?它是否编码了你前进的方向,而不仅仅是当前位置?
  3. 先行指标 — 它是否预测未来的收入和留存,还是仅报告过去的结果?
  4. 可操作 — 产品团队能否通过日常工作影响它?如果你能通过一个单一改动直接移动你的NSM,那它可能太窄了。如果没有团队能移动它,那它太抽象了。
  5. 可衡量 — 你今天就能实现它,还是它是理想化的?(理想化也可以,只要你有计划实现它。)
  6. 难以操纵 — 团队能否通过不当激励达到这个数字?如果能,你需要什么对抗指标?

步骤4:推荐一个NSM

选择最强的一个候选指标并解释原因。直接说明权衡。没有完美的指标——解释这个指标捕捉了什么以及遗漏了什么(以及输入指标如何弥补)。

步骤5:定义输入指标

提出3-5个驱动NSM的输入指标。在适用的情况下,使用广度-深度-频率-效率模式进行组织:

  • 广度 — 有多少客户获得了价值?(例如:活跃账户、激活用户)
  • 深度 — 每个客户获得多少价值?(例如:采用的功能、每个用户运行的查询数)
  • 频率 — 他们多久回来一次?(例如:每周会话、每月活跃天数)
  • 效率 — 通往价值的路径有多无摩擦?(例如:首次洞察时间、注册完成率)

对于每个输入指标,解释:

  • 它衡量什么以及为什么重要
  • 哪个团队可以直接影响它
  • 它与NSM在数学上是如何关联的(加性、乘性或相关性)

步骤6:验证系统

检查完整的指标系统是否协调一致:

  • 如果所有输入指标都改善了,NSM是否必然改善?
  • 如果NSM改善了,业务关键绩效指标(收入)最终是否跟进?
  • 是否存在空白——客户价值的重要方面没有任何指标衡量?
  • 是否存在冲突——优化一个输入是否会损害另一个输入?

指出任何结构性弱点并建议如何解决。

输出格式

提供:

  1. 游戏分类及理由
  2. NSM候选指标(好的和差的)及评估分数
  3. 推荐的NSM及理由
  4. 输入指标及归属责任和关联关系
  5. 系统验证及任何空白或风险
  6. 建议的下一步行动——一旦NSM定义完毕,要做什么(实现它、构建仪表盘、设定目标)

要有主见。一个模棱两可的“看情况”的回答比一个有保留的强有力推荐更糟糕。


提示

  • 带上你的产品描述、当前指标、客户细分和商业模式。背景信息越多,推荐越好。
  • 如果你已经有北极星候选指标,分享它——该技能会对其进行压力测试,而不是从头开始。
  • 收入永远不是NSM,但一定要验证你的NSM预测收入。如果不,那就有问题。
  • 与 build-metric-tree 配合使用,一旦你定义了NSM,就可以将其拆解成一个完整的量化树。
  • 每年或当策略发生变化时重温。一个好的NSM持续1-3年,而不是永远。

延伸阅读

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.

相关技能