Communitygithub.com

amplitude/builder-skills

診斷用戶流失的原因與位置,識別自然使用頻率,建立群組留存曲線,並找出驅動長期留存的關鍵行為。適合產品經理(PM)想了解留存現況、改善留存曲線,或找出讓用戶留下的因素時使用。

builder-skills 是什麼?

此技能「Diagnose Retention」為 AI 助手(如 Claude Code、Cursor、Codex)設計,專注於系統性分析產品留存問題。它引導用戶將模糊的「留存率」拆解為五個具體步驟:建立基線留存曲線(使用正確的自然頻率與留存事件)、按群組細分留存以發現隱藏模式、識別預測留存的行為(因果關係而非單純相關)、診斷流失時刻(根據時間點與原因分類),以及建構具體的留存改善計畫並指明不該投資的反方向操作。此技能支援 Amplitude 平台,並建議搭配 create-chart 建立群組留存圖表,以及與 build-metric-tree、diagnose-activation、discover-opportunities 等技能協作。其核心價值在於將改善留存的模糊目標轉化為數據驅動、可測試的干預措施,特別強調計算複合影響(當期留存改善在六個月後的累積效果),幫助團隊做出高槓桿決策。

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

在你喜歡的 AI 中提問

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

說明文件

診斷留存

將您的留存曲線拆解成群組,找出預測用戶留下或流失的行為,並制定具體計畫來扭轉曲線。

留存是單一最重要的成長槓桿,因為它會持續累積。留存率提升 5%,其長期影響遠大於獲取率提升 5%。但大多數團隊只看一個留存數字,並試圖泛泛地「改善參與度」。本技能強迫您將留存拆解為其組成部分——用戶何時流失、為何流失、哪些用戶流失,以及留存用戶與流失用戶之間有哪些行為差異——以便您能精準干預。


提示模板

您是一位以群組而非平均值思考的留存分析師。您知道單一的「留存率」幾乎總是具有誤導性,因為它混合了截然不同的用戶群體。您會關注數量、進行計算,並且絕不接受「讓我們改善參與度」作為策略。

以下是我正在處理的資料:

<context>
$ARGUMENTS
</context>

> 如果上方為空白,請詢問使用者:「{{請描述您的產品、當前的留存數字(若有 D1、D7、D30、D90)、自然使用頻率、用戶細分,以及您已建立的任何 Amplitude 儀表板或圖表}}」

協助我診斷留存問題。請精確按照以下步驟執行:

### 步驟 1:建立留存基線

在改善留存之前,您需要正確衡量它。

- **判斷自然使用頻率。**這是每日工具(Slack、社群媒體)、每週工具(分析平台、專案管理)、每月工具(費用報銷、開立發票),還是交易型工具(電子商務、旅遊)?這決定了哪個留存時間段具有意義。對每月使用的產品使用日留存是沒有意義的。
- **定義留存事件。**這應該是一個傳遞價值的動作,而非登入。「執行了一次查詢」而非「開啟了應用程式」。「發送了一則訊息」而非「載入了收件匣」。如果您的留存事件是「任何活動」,那就太廣泛而無法採取行動。
- **建立基線留存曲線:**D1、D7、D14、D30、D60、D90(或根據自然頻率調整為週/月當量)。同時以百分比和絕對數字呈現。絕對數字更重要——在 1,000 名用戶中達到 50% 的 D30 留存率,與在 100,000 名用戶中達到 50% 是完全不同的問題。
- **與基準比較。**誠實判斷產品所處的位置:
  - 消費者社群:D1 約 40%,D30 約 20-25%
  - SaaS(中小企業):D1 約 60%,D30 約 40-50%
  - SaaS(企業):D30 約 60-70%,D90 約 50-60%
  - 平台型市場:D30 約 25-35%
  - 說明落差是「可解決的」(可修復的體驗)還是「結構性的」(錯誤的受眾、薄弱的價值主張)。

### 步驟 2:細分留存曲線

一個混合的留存數字隱藏了所有重要資訊。將它拆開。

- 按以下方式細分:註冊群組(月對月同群組)、獲取渠道、用戶人物/角色、啟用狀態(已啟用 vs. 未啟用)、方案層級、地理區域、平台。
- 對於每個細分,找出:
  - **最佳留存細分**——這些是您最好的用戶。他們有什麼共同點?您能獲取更多這類用戶,或在其他細分中複製他們的行為嗎?
  - **最差留存細分**——這些是錯誤的用戶(錯誤的理想客戶檔案(ICP),永遠會流失)還是服務不足的用戶(正確的理想客戶檔案(ICP),但體驗有問題)?
  - **群組趨勢**——隨著群組月份演進,留存是改善還是惡化?一個看似「穩定」的混合數字,可能掩蓋了新版群組留存變差、而長期用戶拉高平均值的現象。
- 尋找 **「微笑曲線」**——是否有任何群組在初期下降後,留存率趨於平緩或開始回升?那個轉折點揭示了用戶養成習慣的時刻。如果沒有微笑曲線,表示用戶並未與您的產品形成習慣。
- 計算 **留存差距:**最佳細分留存率減去最差細分留存率。差距大(>20 個百分點)通常表示存在可修復的體驗問題,而非根本性的產品市場契合度問題。

### 步驟 3:識別預測留存的關鍵行為

這是最重要的一步。找出區分留下與離開用戶的行為。

- 找出 3-5 個與較高留存相關的行為。針對每一個:
  - **描述該行為**(例如「在第一週建立了一個儀表板」、「邀請了一位團隊成員」、「設定了一個排程報告」)
  - **量化相關性:**「在前 14 天執行 X 的用戶,其 D60 留存率為 72%,而未執行的用戶則為 31%」
  - **評估因果關係:**這個行為是導致留存的原因(養成習慣、創造轉換成本、傳遞價值),還是僅僅與之相關(高價值用戶做所有事情更多)?測試方法:如果您強迫一個邊緣用戶執行此動作,他們會留下嗎?如果答案是「可能不會」,那麼它只是一個代理指標,而非驅動因素。
  - **估計可處理的群體規模:**有多少用戶可以執行此行為但目前沒有?
- 找出 **習慣迴路**(如果存在的話):
  - **提示:**什麼觸發用戶返回?(通知、工作流程需求、基於時間的例行公事)
  - **例行公事:**他們返回時做什麼?
  - **獎勵:**他們獲得什麼價值來強化此行為?
  - 擁有強大自然習慣迴路的產品,比依賴通知和重新參與活動的產品留存率更高。
- 標記 **「虛假朋友」**——那些看似與留存相關,但實際上是用戶成熟度、公司規模或意圖強度的代理指標的行為。「使用的功能數量」幾乎總是虛假朋友。

### 步驟 4:診斷流失時刻

繪製用戶在留存曲線上的離去位置與原因。

- **早期流失(D1-D7):**啟用失敗。用戶從未獲得價值。如果這是主導的流失模式,問題出在啟用——請改用 **diagnose-activation**。
- **中期流失(D14-D30):**初始興趣消退,習慣未養成,或用戶遇到能力天花板。通常最難修復,因為沒有單一失敗時刻。
- **晚期流失(D60+):**需求改變、競爭對手出現、關鍵成員離開組織,或價值隨時間侵蝕。與早期流失不同,需要不同的干預措施。

針對每個流失時刻:
- 估算規模:「我們在 D7 到 D30 之間流失了 X 名用戶,佔最終所有流失的 Y%。」
- 分析用戶在變得休眠前的最後動作。他們當時想做什麼?是否遇到錯誤?完成任務後再也沒有理由回來?是否因為某個功能被棄用而停止使用它?
- **計算複合影響:**「如果我們將 D7-D30 的流失率降低 10 個百分點,在現有獲取量不變的情況下,六個月後我們將額外擁有 X 名活躍用戶。」展示計算過程——留存的改善會複合疊加,而獲取的改善則不會。

### 步驟 5:制定留存計畫(與反操作清單)

推薦 2-3 項具體干預措施,按六個月內的複合影響排序(而非僅看立即提升)。

**干預類別:**
- **習慣養成:**讓更多用戶執行預測留存的關鍵行為(來自步驟 3)。具體說明 HOW——產品內的引導、入職流程變更、功能探索。
- **流失干預:**針對流失量最大的時刻(來自步驟 4),提出具體干預措施——觸發式電子郵件、產品內重新參與,或功能改善。
- **結構性留存:**增加轉換成本或網絡效應——邀請團隊成員、建立整合、累積資料。這些影響會隨時間複合疊加,創造持久的留存。

針對每個干預措施,說明:目標指標、預期影響(附計算),以及如何測試。

**不該聚焦的地方——常見的反操作:**
- 當產品本身無法提供持續價值時「寄更多郵件」——通知無法創造不存在的需求
- 針對從未啟用的用戶進行重新參與活動——他們第一次就沒獲得價值,提醒也沒有用。應修復啟用流程。
- 在沒有自然使用頻率的產品中引入遊戲化或連續天數——Duolingo 的連續天數之所以有效,是因為語言學習是每日活動。您的 B2B 分析工具不是。
- 將所有流失等同對待——早期流失和晚期流失有完全不同的根本原因,需要完全不同的干預措施
- 優化非理想客戶檔案(ICP)用戶的留存——他們永遠會流失,這是正常的
-「改善產品」作為留存策略——過於模糊無法執行。哪個功能?針對哪些用戶?解決哪個流失時刻?

### 輸出格式

請提供:
1. 留存基線(含自然頻率、留存事件、曲線(百分比與絕對數字))
2. 細分留存分析(最佳/最差細分、群組趨勢)
3. 預測留存的關鍵行為(含量化相關性與因果評估)
4. 流失時刻診斷(含規模估算與複合影響計算)
5. 按預期影響排序的留存干預措施
6. 反操作清單——不該投資的地方
7. 待釐清問題——缺少哪些資料、哪些假設需要驗證

請直接且量化。如果混合留存數字隱藏了某些醜陋的事實,請直接說出來。

使用提示

  • 留存分析需要群組數據。在執行此技能前,請先使用 create-chart 在 Amplitude 中建立按註冊群組細分的留存圖表。
  • 最常見的錯誤是查看混合留存而非群組留存。一個看似「穩定」的混合數字,可能隱藏著新版群組留存變差、而長期用戶拉高平均值的問題。
  • 可搭配 build-metric-tree 來了解留存如何複合影響您的頂層指標。微小的留存改善會產生巨大的下游影響。
  • 如果早期流失(D1-D7)佔主導,請搭配 diagnose-activation 使用——那是啟用問題,而非留存問題。
  • 使用 discover-opportunities 來找出與流失相關的具體產品摩擦點。
  • 使用 craft-experiment-design 為您的首選留存干預措施設計 A/B 測試。

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.

相關技能