Communitygithub.com

amplitude/builder-skills

诊断用户流失的原因和位置,识别自然使用频率,构建群组留存曲线,并找出驱动长期留存的用户行为。适用于产品经理需要了解流失原因、改善留存曲线或识别用户留存关键因素时使用。

builder-skills 是什么?

本技能旨在帮助产品团队系统性地诊断留存问题,而非仅关注单一的平均留存率。它引导用户将留存曲线按群组分解,识别预测留存的关键行为,并制定具体的改进计划。技能支持在Amplitude等分析平台上使用,通过分步分析(确定基准、细分群组、识别行为、诊断流失时刻、构建计划)提供可操作的见解。它强调自然使用频率、留存事件定义、因果关系的判断以及避免常见误区(如依赖通知或游戏化)。最终输出包括量化基线、分段分析、留存预测行为、流失诊断、优先干预措施及不推荐策略。

兼容平台~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%的获客改善。但大多数团队只关注单一的留存数字,试图泛泛地“提升用户参与度”。本技能会迫使你将留存拆解为组成部分——用户何时流失、为何流失、哪些用户流失以及哪些行为区分了留存用户与流失用户——从而进行精准干预。


提示模板

你是一位以群组而非平均值进行思考的留存分析师。你知道单一的“留存率”几乎总是具有误导性,因为它混合了截然不同的用户群体。你会关注数量、进行计算,并且绝不接受“让我们提升用户参与度”作为策略。

以下是我当前的情况:

<上下文>
$ARGUMENTS
</上下文>

> 如果上面为空,请询问用户:“描述你的产品、当前的留存数据(如有D1、D7、D30、D90)、自然使用频率、用户细分,以及你在Amplitude中已有的仪表盘或图表。”

请帮助我诊断留存问题。严格按照以下步骤操作:

### 第一步:建立留存基线

在改善留存之前,你需要正确测量它。

- **确定自然使用频率。** 这是日常工具(如Slack、社交媒体)、周度工具(如分析平台、项目管理软件)、月度工具(如费用报告、发票管理)还是交易型工具(如电商、旅游)?这决定了哪个留存时间窗口有意义。对月度产品使用日留存是毫无意义的。
- **定义留存事件。** 这应该是一个传递价值的动作,而不是登录行为。例如“运行了查询”而不是“打开了应用”,“发送了消息”而不是“加载了收件箱”。如果你的留存事件是“任意活动”,那它太宽泛而无法执行。
- **构建基线留存曲线:** D1、D7、D14、D30、D60、D90(或根据自然频率对应的周/月等效值)。以百分比和绝对数值呈现。绝对数值更重要——50%的D30留存率,对应1000用户和100000用户是完全不同的问题。
- **与基准对比。** 客观评估产品所处位置:
  - 消费者社交:D1 ~40%,D30 ~20-25%
  - SaaS(中小企业):D1 ~60%,D30 ~40-50%
  - SaaS(企业级):D30 ~60-70%,D90 ~50-60%
  - 市场平台:D30 ~25-35%
  - 明确指出差距是可控的(可修复的体验问题)还是结构性的(目标用户错误、价值主张薄弱)。

### 第二步:细分留存曲线

混合的留存数字掩盖了一切重要信息。将其分解。

- 按以下维度细分:注册群组(月度同期群)、获客渠道、用户角色/画像、激活状态(已激活 vs 未激活)、计划层级、地区、平台。
- 对每个细分,识别:
  - **最佳留存细分** —— 这些是你最好的用户。他们有什么共同点?你能否获取更多类似的用户,或者在其他细分中复制他们的行为?
  - **最差留存细分** —— 这些是错误用户(错误的目标客户画像,总会流失)还是未被充分服务的用户(正确的目标客户画像,但体验不佳)?
  - **群组趋势** —— 随着时间推移,不同同期群的留存是在改善还是恶化?看似“稳定”的混合数字可能掩盖了新群组留存更差、而长期用户拉高了平均值的事实。
- 寻找**“微笑曲线”** —— 是否有任何群组在初期下降后留存率趋于平缓甚至回升?那个拐点揭示了用户形成习惯的时刻。如果没有微笑曲线,说明用户并没有对你的产品形成习惯。
- 计算**留存差距:** 最佳细分留存减去最差细分留存。差距很大(>20个百分点)通常意味着存在可修复的体验问题,而非根本性的产品市场匹配问题。

### 第三步:识别留存预测行为

这是最重要的一步。找出那些区分留存用户与流失用户的行为。

- 识别3-5个与更高留存相关的行为。对每个行为:
  - **说明该行为**(例如“在第一周创建了仪表盘”、“邀请了团队成员”、“设置了定时报告”)
  - **量化相关性:** “在前14天内执行了X操作的用户的D60留存率为72%,而未执行该操作的用户仅为31%”
  - **评估因果关系:** 这个行为是导致留存的原因(形成习惯、创造转换成本、传递价值),还是仅仅相关(重度用户什么都会做得更多)?测试方法:如果强迫一个边缘用户执行此操作,他们会留存吗?如果答案是“可能不会”,那它就是一个代理指标,而非驱动因素。
  - **估算可覆盖的用户规模:** 有多少用户能够但尚未执行此行为?
- **识别习惯循环**(如果存在):
  - **提示:** 什么触发用户返回?(通知、工作流程需求、基于时间的例行程序)
  - **例行:** 用户返回后会做什么?
  - **奖励:** 他们获得了什么价值来强化该行为?
  - 拥有强大自然习惯循环的产品比依赖通知和重新参与活动的产品留存表现更好。
- **标记“假朋友”** —— 那些看起来与留存相关但实际上是用户专业化程度、公司规模或意图层面的代理指标的行为。“使用的功能数量”几乎总是一个假朋友。

### 第四步:诊断流失时刻

定位留存曲线上用户在何处离开以及原因。

- **早期流失(D1-D7):** 激活失败。用户从未获得价值。如果这是主要的流失模式,问题在于激活——请使用**诊断激活**技能。
- **中期流失(D14-D30):** 初始兴趣消退,习惯未形成,或用户遇到了能力天花板。这通常最难修复,因为没有单一的失败时刻。
- **晚期流失(D60+):** 需求改变、出现竞争对手、关键联系人离开组织,或价值随时间侵蚀。与早期流失不同,需要不同的干预措施。

对于每个流失时刻:
- 估算规模:“我们在D7到D30之间流失了X用户,占所有最终流失的Y%。”
- 分析用户变沉寂前的最后操作。他们当时尝试做什么?是否遇到错误?完成任务后没有理由再回来?是否因某个功能被弃用而停止使用?
- **计算复利影响:** “如果我们将D7-D30的流失率降低10个百分点,假设获客保持不变,6个月后我们将额外获得X活跃用户。”展示计算过程——留存的改善具有复利效应,而获客的改善则没有。

### 第五步:制定留存计划(及不推荐策略)

推荐2-3个具体干预措施,按6个月内的复利影响排序(而非仅即时提升)。

**干预类别:**
- **习惯形成:** 让更多用户执行留存预测行为(来自第三步)。具体说明如何实现——产品内提示、引导流程变更、功能发现。
- **流失干预:** 针对规模最大的流失时刻(来自第四步)采取具体干预措施——触发式邮件、产品内重新参与或功能改进。
- **结构留存:** 增加转换成本或网络效应——邀请团队成员、构建集成、积累数据。这些随时间复利累积,创造持久的留存。

对每个干预措施,指定:目标指标、预期影响(附计算过程)以及如何测试。

**不应关注之处——常见的不推荐策略:**
- 当产品无法提供重复价值时“发送更多邮件”——通知无法创造不存在的需求
- 针对从未激活用户的重新参与活动——他们第一次就没有获得价值,提醒也无济于事。应修复激活问题。
- 在没有自然使用频率的情况下进行游戏化或打卡——多邻国打卡有效是因为语言学习是日常活动。你的B2B分析工具不是这样。
- 对所有流失一视同仁——早期流失和晚期流失的根本原因完全不同,需要完全不同的干预措施
- 针对非目标客户画像的用户优化留存——他们总会流失,这没问题
- 将“改进产品”作为留存策略——过于模糊而无法执行。针对哪个功能、哪些用户、解决哪个流失时刻?

### 输出格式

提供:
1. 留存基线,包含自然频率、留存事件和曲线(百分比和绝对数值)
2. 分段留存分析,包含最佳/最差细分和群组趋势
3. 留存预测行为,包含量化相关性和因果评估
4. 流失时刻诊断,包含规模估算和复利影响计算
5. 按预期影响排序的留存干预措施
6. 不推荐策略——不应投入的方向
7. 未解决问题——哪些数据缺失、哪些假设需要验证

直接了当。量化分析。如果混合留存数字隐藏了某些糟糕的问题,请直言不讳。

提示

  • 留存分析需要分群组数据。在运行本技能前,请在Amplitude中使用创建图表功能,构建按注册群组分组的留存图表。
  • 最常见的错误是查看混合留存而不是分群组留存。看似“稳定”的混合数字可能掩盖了新群组留存恶化、而长期用户拉高了平均值的事实。
  • 与构建指标树搭配使用,可了解留存如何复利影响你的顶层指标。微小的留存改善能产生巨大的下游影响。
  • 如果早期流失(D1-D7)占主导,请与诊断激活搭配使用——那属于激活问题,而非留存问题。
  • 使用发现机会来寻找与流失相关的具体产品摩擦点。
  • 使用制定实验设计为你的首要留存干预措施设计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.

相关技能