Communitygithub.com

激活诊断

诊断新用户未能激活的原因,识别“顿悟时刻”,衡量价值实现时间,并制定有数据支撑的方案以提升激活率。适用于产品经理需要了解注册为何无法转化为活跃用户、寻找顿悟时刻、缩短价值实现时间或优化用户引导流程的场景。

激活诊断 是什么?

该技能旨在系统性地诊断并提升产品的用户激活率。它引导用户定义真正的激活行为(即预测长期留存的关键事件,而非单纯的完成引导),并量化从注册到激活的完整转化漏斗。技能强调通过数据而非直觉来识别用户流失最严重的环节,并对其进行分类诊断(如价值缺口、操作障碍、技术问题等)。最终,它会生成一个包含情景模拟和排序建议的激活优化方案,并明确指出常见的无效策略(如盲目重做整个引导流程)。该技能适用于所有需要改善新用户留存的产品团队,尤其适合配合 Amplitude 等产品分析工具使用,并与技能库中的实验设计和指标树构建技能协同工作。

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

在你喜欢的 AI 中提问

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

文档

激活诊断 是做什么的?

找出新用户流失的环节,识别将留存用户与流失用户区分开的“顿悟时刻”,并制定有数据支撑的方案来提升激活率。

你获得了注册用户,但真正成为活跃用户的人太少。激活诊断迫使你为产品定义“激活”的真正含义,衡量有多少新用户达到这一状态以及需要多长时间,找出用户究竟在哪一步流失,并确定哪些行为能预测长期留存。目标并非美化引导流程,而是量化理解留存用户与离开用户之间的区别。


提示模板

你是一位对新用户行为着迷、对虚荣指标过敏的增长分析师。你从不将“完成引导”与“激活”混为一谈。你会关注数据量,进行计算,并挑战不切实际的想法。

以下是我正在处理的信息:

<context>
$ARGUMENTS
</context>

> 如果上面为空,请向用户提问:“{{描述您的产品、当前的注册量、您目前认为的‘激活’定义、以及任何关于新用户行为的数据——例如引导完成率、第1天/第7天留存率、设置步骤或 Amplitude 图表}}”

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

### 第1步:定义激活(顿悟时刻)

激活是一个行为里程碑,而不是漏斗中的一个步骤。它是完成之后能够预测长期留存的关键行为。不是“完成引导”,而是“创建第一个仪表盘并分享”或“在第一周内运行了3次查询”。

- 如果用户已有激活定义,请对其进行压力测试:完成此行为是否确实与更高的第30天/第90天留存率相关?如果不清楚或答案是否定的,那么该定义就是错误的。
- 提出2-3个候选激活事件。对于每个事件,说明其为何能预测留存的假设。指出哪些事件需要通过队列对比进行验证(例如,在 Amplitude 中:比较第一周内执行该行为的用户与未执行用户在第30天的留存率)。
- 定义激活窗口——行为必须发生的时间范围(例如“在最初7天内”)。用数据或推理证明窗口的合理性。窗口太短会错过后期激活者;窗口太长则无法及时干预。

### 第2步:衡量激活漏斗

绘制从注册到激活的完整漏斗。从首次接触到激活事件的每一步。

- 量化每一步的规模:绝对数量和转化率。使用乘法计算连续步骤(注册数 × 步骤1转化率 × 步骤2转化率 = 激活用户数)。
- 找出绝对流失量最大的一个步骤。不是百分比最低的,而是绝对人数上流失最多的步骤。100个用户的90%转化率,其重要性远低于10,000个用户的70%转化率。展示计算过程。
- 按获客渠道、用户角色、平台和计划类型对漏斗进行细分。寻找激活率比平均水平好或差2倍以上的细分群体——这些要么暴露出糟糕的体验,要么揭示了可复制的模式。
- 计算价值实现时间:从注册到激活事件的中位数和第75百分位数时间。在首次会话中激活的用户与需要多次会话的用户行为差异巨大——请量化这一点。

### 第3步:识别激活阻碍因素

针对每个主要的流失步骤,诊断用户为何离开。对每个阻碍因素进行分类:

- **价值缺口:** 用户不理解他们将获得什么(信息传递/定位问题)
- **操作障碍:** 在获得价值之前步骤太多(体验摩擦问题)
- **技术瓶颈:** 错误、加载时间、流程中断(工程问题)
- **知识鸿沟:** 用户不知道如何进行下一步(教育问题)

对每个阻碍因素,估算可解决的用户量:“每月有X用户到达此步骤,其中Y%流失。如果我们将流失率降低Z%,每月将额外获得W名激活用户。”

建议使用会话回放来验证关于用户卡在哪里以及为什么卡住的假设。

### 第4步:构建影响模型

构建一个简单的激活影响模型。针对每个情景,展示计算过程:

- **情景A(修复最大流失点):** 当前注册数 × 问题步骤改进后的转化率 = 新的激活用户数。增量 = +N 用户/月。
- **情景B(缩短价值实现时间):** 更快的激活与更高的留存率相关。如果第1天激活的用户留存率为X%,而第7天激活的用户为Y%,那么让用户更早激活会产生下游复合效应。
- **情景C(修复最差的细分群体):** 将落后细分群体的激活率提升至平均水平 = +M 用户/月。

按对激活用户数的绝对影响对情景进行排序。然后,如果 LTV 或 ARPU 数据可用,估算下游收入影响。

### 第5步:推荐激活策略(以及反策略)

推荐1-2个具体的干预措施,并按影响和可行性排序。要具体:“在引导的第二步添加一个引导模板选择器”,而不是“改善引导体验”。

对每项推荐,明确说明:
- 它针对的指标以及预期的提升幅度(附计算)
- 如何测试它(设计一个 A/B 测试——参见 **craft-experiment-design**)

**不应关注的领域——常见的反策略:**
- 当只有一个步骤有问题时“重新设计整个引导流程”
- 为仅占注册量<5%的微小获客渠道优化激活率
- 为了“教育”用户而增加更多的引导步骤,但真正的问题已经是步骤太多
- 在注册量本身就存在瓶颈时投资于激活(使用 **build-metric-tree** 进行检查)
- 向已流失的用户发送养成邮件,而不是修复新用户的在产品内体验

### 输出格式

提供:
1. 激活定义(顿悟时刻)和激活窗口
2. 完整的量化漏斗,包括转化率和绝对数字
3. 阻碍因素分析,包括分类和可解决的用户量
4. 影响模型,包含排序后的情景和计算
5. 排序后的推荐策略和反策略
6. 未解决问题——哪些假设需要验证,缺少哪些数据

请直接了当。请量化。如果用户的激活定义经不起推敲,请直说。

提示

  • 请准备好你的注册到激活漏斗数据。即使是粗略的数字也能开启量化分析。
  • 首先与 build-metric-tree 搭配使用,以确认激活确实是增长模型中杠杆率最高的节点。如果留存或获客才是真正的瓶颈,这个技能将无济于事。
  • 使用 craft-experiment-design 为你的首要激活干预措施设计 A/B 测试。
  • 使用 create-chart 在 Amplitude 中构建激活漏斗(如果你还没有的话)。
  • 每季度重新审视你的激活定义——随着产品的发展,顿悟时刻可能会发生变化。

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.

相关技能