Communitygithub.com

amplitude/builder-skills

定義北極星指標及其輸入指標。對產品所屬的遊戲類型進行分類,根據品質標準評估候選指標,並建立一套相互連結的指標系統。適用於選擇北極星指標、評估現有指標或建立指標架構時使用。

builder-skills 是什麼?

此技能旨在幫助團隊定義一個真正的北極星指標(North Star Metric, NSM),這是一個以客戶為中心、能夠反映產品創造價值的單一核心指標。它引導使用者逐步完成整個過程:首先將產品分類為注意力(Attention)、交易(Transaction)或生產力(Productivity)這三種遊戲類型之一;然後生成並評估多個候選NSM,並對其品質標準(如客戶價值、策略清晰度、可執行性等)進行評分。接著,技能會協助選擇最佳候選指標,並定義3-5個可操作的輸入指標(如廣度、深度、頻率、效率),以驅動該北極星指標,最終驗證整個指標系統是否預測了關鍵業務績效指標(如營收)。此技能支援廣泛的產品策略與成長框架平台,透過結構化的對話與意見領袖般的建議,幫助團隊擺脫虛榮指標,專注於真正驅動長期業務成功的指標。

相容平台~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 應該預測營收,而不是成為營收本身。
  • 不是 DAU 或註冊用戶。 這些是虛榮指標 — 它們表面上好看,但無法告訴你客戶是否獲得了價值。
  • 不是 OKR。 OKR 是目標設定工具。你可以使用關鍵結果來表達 NSM 的預期變化,但兩者是不同的東西。
  • 不是多個指標。 每條產品線只有一個 NSM。如果你有多個相互競爭的北極星,那就等於沒有北極星。

三種遊戲

在選擇你的 NSM 之前,先分類你的產品屬於哪種遊戲類型:

  • 注意力遊戲 — 成功 = 在產品中花費的時間。用戶為了內容、娛樂或持續參與而來。(例如:Netflix, Spotify, TikTok)
  • 交易遊戲 — 成功 = 交易量。用戶為了買賣或交換價值而來。(例如:Amazon, Airbnb, Stripe)
  • 生產力遊戲 — 成功 = 有效率地完成工作。用戶為了更快或更好地完成任務而來。(例如:Notion, Figma, Amplitude)

大多數產品只玩一種遊戲。試圖玩遍所有三種會分散焦點。在選擇指標之前,先了解你的遊戲類型。

指標系統:NSM + 輸入指標 + 業務 KPI

北極星指標無法單獨運作。你需要三個層級:

  1. 北極星指標 — 整體客戶價值(例如,教育產品的「每週學習時數」)
  2. 輸入指標 (3-5 個) — 可控的、互補的因素,驅動著 NSM。一個有用的模式是:廣度(有多少客戶?)、深度(每個客戶有多少價值?)、頻率(多久一次?)、效率(多快/多無摩擦?)。這些是團隊日常工作中真正能推動的。
  3. 頂層業務 KPI — 回饋給業務的價值(營收、付費席位、ARR)。這必須與 NSM 在結構上連結起來。如果 NSM 上升但業務 KPI 沒有,表示你有變現問題。如果業務 KPI 上升但 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 改善了,業務 KPI(營收)最終是否會跟上?
  • 是否存在缺口 — 客戶價值的某些重要方面沒有被任何指標衡量到?
  • 是否存在衝突 — 最佳化某個輸入指標是否會傷害另一個?

標記任何結構性弱點,並建議如何解決它們。

輸出格式

提供:

  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.

相關技能