Communitygithub.com

amplitude/builder-skills

診斷營收流失、分析用戶付費意願、評估方案組合與定價,並找出擴張營收的機會。適用於產品經理需要改善免費轉付費轉換率、優化定價、降低營收流失,或尋找增購與擴張機會的情境。

builder-skills 是什麼?

此技能專注於貨幣化診斷,協助產品經理與成長團隊系統性地分析營收架構,找出價值與價格之間的缺口。它涵蓋五個核心步驟:首先解構營收公式(用戶數 x 轉換率 x ARPU x 留存率 + 擴張營收),並評估各項指標;接著深入分析免費轉付費漏斗,區分「永遠免費使用者」與「未來付費潛在用戶」;第三步評估方案包裝與定價,判斷是否有過度閘控、閘控不足或價值指標錯置的問題;第四步分析擴張與收縮,找出淨營收留存率(NRR)的驅動因子;最後建立一個風險調整後的營收機會矩陣,並明確列出不該投入的「反模式」。輸出的報告包含量化的營運建議、敏感性分析,以及待驗證的假設清單。支援平台包括 Amplitude、Claude Code 等 AI 代理工具,並建議搭配 experiment-design、build-metric-tree 及 retention-diagnosis 等技能使用,以確保定價變更前的全面驗證。

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

在你喜歡的 AI 中提問

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

說明文件

診斷貨幣化

找出營收流失點、從用戶行為中辨識付費意願訊號、評估你的方案包裝,並量化你能夠捕捉更多價值的機會。

你正在傳遞價值,卻未能按比例將價值轉化為營收。貨幣化診斷不是盲目調漲價格——而是理解用戶獲得的價值與你收取的營收之間的關係,找出缺口並加以填補。最佳的貨幣化改善來自於讓價格與價值對齊:在你提供更多價值的地方收取更高費用,移除阻礙採用的付費摩擦,並從那些已經證明需要你的用戶身上擴張營收。


提示模板

你是一位貨幣化策略師,理解定價是產品決策,而非財務決策。你跟隨價值走,量化每個機會,並且在未理解對轉換率與留存率的行為影響之前,從不建議調價。

以下是我目前的情況:

<context>
$ARGUMENTS
</context>

> 如果上方為空白,請詢問使用者:「{{請描述你的產品、定價模式(免費/免費增值/試用/付費方案)、當前營收指標(ARR、ARPU、轉換率、擴張率、營收流失率)、用戶分群,以及各方案的任何功能使用數據}}」

請協助我診斷貨幣化。請精確遵循以下步驟:

### 第一步:繪製營收架構

首先解析營收如何產生以及在何處流失。

- **以數學方式分解營收:** 營收 = 用戶數 × 轉換率 × ARPU × (1 - 營收流失率) + 擴張營收。用實際數字量化每個組成部分。
- **繪製每個方案/計劃:** 針對每個方案——價格、包含內容、當前用戶數、從前一方案的轉換率、ARPU。
- **找出價值指標** —— 隨使用量擴張並應驅動定價的價值單位(席位數、追蹤的事件數、執行的查詢數、建立的專案數、API 呼叫數)。評估當前定價是否與此價值指標相符。如果你按席位收費,但價值隨使用量擴張,就存在結構性的錯位,導致營收流失。
- **計算各分群的 LTV:CAC**(如有數據)。LTV:CAC > 3 的分群屬於貨幣化不足或獲取投資不足;LTV:CAC < 1 的分群則在破壞價值——你花費更多成本獲取他們,而他們永遠無法回報。

### 第二步:診斷免費轉付費漏斗

如果你有免費方案或試用期,這裡是大多數營收流失的地方。

- **繪製轉換漏斗** 從免費/試用到首次付款。用絕對數字和比率量化每個步驟。
- **找出轉換觸發條件** —— 什麼行為或事件會促成轉換?常見觸發條件:
  - 達到使用限制(自然付費牆)
  - 需要僅付費才有的功能(功能閘門)
  - 團隊擴張(席位觸發)
  - 合規或管理需求(企業觸發)
- **按以下維度分群分析轉換率:** 獲取管道、用戶角色、公司規模、使用強度、使用時間。找出轉換率為平均值 2 倍以上或 0.5 倍以下的分群——這揭示了方案包裝錯位或目標定位問題。
- **分析轉換所需時間:** 從註冊到首次付款需要多久?是否存在自然的轉換窗口?繪製隨時間變化的轉換機率——在此窗口內未轉換的用戶,之後很少會轉換。量化衰減曲線。
- **區分「永遠免費使用者」與「未來潛在付費用戶」:**
  - **永遠免費使用者:** 大量使用免費功能但永遠不會付費的用戶——他們繞過限制、使用免費替代方案應對付費功能,或屬於沒有預算的分群。量化此群體規模。
  - **未來潛在付費用戶:** 正在朝觸發條件前進的用戶——使用量增加、加入團隊成員、探索付費功能。量化此群體規模。
  - 如果永遠免費使用者群體很大,表示免費方案給出了太多價值。如果未來潛在付費用戶管線薄弱,表示免費方案未能充分展示價值以驅動升級。

### 第三步:評估方案包裝與定價

方案包裝決定誰付費以及付多少。搞錯了,你不是把錢留在桌上,就是阻礙了採用。

- **評估功能與方案的對齊方式。** 針對每個付費功能:
  - 有多少百分比的免費用戶會想要它?
  - 有多少百分比的付費用戶實際使用它?
  - 它是「開門磚」(驅動初始轉換)還是「關門磚」(證明續約合理)?
- **找出方案包裝問題:**
  - **閘控不足:** 高價值功能可免費使用,若加以閘控可能驅動轉換。量化機會:「X 位免費用戶每週使用功能 Y。如果將其閘控於付費方案之後,以當前轉換率計算,每月可帶來 $Z。」
  - **過度閘控:** 功能被鎖定在昂貴的方案中,導致極少用戶能接觸到,進而降低整體採用率並造成網絡效應的損害。如果協作功能被鎖定在企業版,產品對其他所有人來說會感覺空虛。
  - **錯誤的價值指標:** 按席位定價,但價值隨使用量擴張(懲罰協作),或按使用量定價,但價值來自廣度(懲罰探索)。
  - **缺少方案層級:** 定價階梯中存在缺口,導致有意義的用戶分群卡在中間——升級太貴,當前方案又無法提供足夠價值。量化卡在此缺口的用戶規模。
- **從行為中識別付費意願訊號:** 達到限制並繞過它的用戶、請求僅在高級方案中才有的功能的用戶、使用模式符合付費方案設定檔但尚未升級的用戶。這些是轉換率最高的目標。

### 第四步:分析擴張與收縮

對於訂閱制業務,擴張營收通常比新客戶獲取更有機會。

- **分解淨營收留存率(NRR):** 毛留存 + 擴張 - 收縮 - 流失。量化每個組成部分。
- **找出擴張觸發條件:** 什麼原因導致用戶升級?席位增加、使用量成長、功能需求、合規要求?按頻率和營收影響量化每個觸發條件。
- **找出收縮觸發條件:** 什麼原因導致降級?席位減少、使用量下降、功能冗餘、預算削減?量化每個觸發條件。
- **計算擴張營收潛力:** 「方案 A 中 X% 的用戶使用了超過 80% 的額度。如果 Y% 的用戶在達到額度後升級,每月可產生 $Z 的擴張營收。」這是最直接可處理的貨幣化機會。
- **找出「準備擴張」的群組** —— 行為顯示他們需要更高方案但尚未升級的用戶。是什麼阻礙了他們?
  - 價格衝擊(方案間的差距太大)
  - 價值不明確(他們不了解會得到什麼)
  - 摩擦力(升級流程隱藏、需要聯絡銷售人員,或花費太長時間)

### 第五步:量化並排序貨幣化機會(與反模式)

建立一個貨幣化機會矩陣。針對每個機會:

| 機會 | 營收影響($/月) | 受影響用戶數 | 留存風險 | 努力程度 | 見效時間 |
|------|----------------|--------------|----------|----------|----------|
| ...  | ...            | ...          | ...      | ...      | ...      |

- 按 **風險調整後的營收影響** 排序。一個每月增加 50K 美元但導致流失率上升 5% 的變更,可能淨效果為負。為前三大機會展示計算過程。
- **建立敏感性模型:** 「當前流量下,免費轉付費轉換率每提升 1 個百分點 = 每月 $X。當前付費用戶基礎上,ARPU 每增加 $Y = 每月 $Z。」這揭示了轉換率或 ARPU 哪個是更大的槓桿。
- **進行複合計算:** 同時改善留存率的貨幣化改善(更好的價值對齊、移除摩擦)會產生複合效應。損害留存率的貨幣化變更會隨時間侵蝕。務必同時模擬兩種效應。

**不該關注的地方——常見的反模式:**
- 未了解價格敏感度就漲價——你可能增加 ARPU 但降低轉換率,淨效果為負
- 閘控那些驅動啟用或留存的功能——你將用短期營收換取長期流失。如果某功能是讓用戶留下的關鍵,請保持其可及性。
- 在產品市場契合度尚未達成之前優化貨幣化——如果留存率差,調整定價也救不了你。請先使用 **build-metric-tree** 檢查。
- 添加廉價方案以「捕捉更多用戶」,但真正的問題是轉換摩擦而非價格——你將稀釋 ARPU 卻未修復漏斗
- 將所有免費用戶視為「潛在營收」——某些分群永遠不會付費,但如果他們貢獻網路效應、口碑推薦或市場流動性,這也沒問題
- 過度關注 ARPU,而用戶量才是限制因素——使用 **build-metric-tree** 檢查貨幣化或獲取是否為真正的槓桿
- 未了解自己的價值指標與客戶分群是否相同,就複製競爭對手的定價

### 輸出格式

提供:
1. 營收架構,包含分解後的公式及每個組成部分的量化值
2. 免費轉付費漏斗分析,包含轉換觸發條件與轉換所需時間
3. 方案包裝評估,包含具體的閘控不足、過度閘控與錯位發現
4. 擴張/收縮分析,包含 NRR 分解與準備擴張的群組
5. 排序後的貨幣化機會矩陣,包含風險調整後的營收計算
6. 反模式——不該投資的地方
7. 未決問題——缺少哪些數據、哪些假設需要驗證(特別是價格敏感度)

直接了當。用量化說話。如果定價模型與價值傳遞存在結構性錯位,請明確說出。

提示

  • 貨幣化變更風險高且難以逆轉。務必在推出定價或方案包裝變更之前,搭配 craft-experiment-design 使用。
  • 帶入按方案與分群的營收數據。即使是大約的 ARPU 與轉換率,也能解鎖量化步驟。
  • 先使用 build-metric-tree 確認貨幣化確實是瓶頸——如果獲取或留存出了問題,修正貨幣化也救不了你。
  • 使用 create-chart 在 Amplitude 中建立各方案的功能使用圖表。這在第三步的方案包裝評估中至關重要。
  • 使用 diagnose-retention 了解營收流失是來自產品留存問題還是定價不滿——兩者的干預措施完全不同。
  • 如果你有免費方案,最具影響力的分析就是找出轉換觸發條件。一旦知道是什麼讓用戶付費,你就可以引導更多用戶邁向那個時刻。

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.

相關技能