Communitygithub.com

amplitude/builder-skills

诊断用户来源、衡量渠道效率、识别自然与付费流量健康度、按细分客群计算CAC,并找到最高杠杆的获客渠道。当产品经理需要理解获客经济性、优化渠道组合或找出增长在漏斗顶部停滞的原因时使用。

builder-skills 是什么?

该技能帮助产品经理和增长团队系统地诊断获客表现,超越简单的流量虚荣指标。它要求分解各渠道的注册量,衡量每个渠道的真实成本与下游质量(包括激活率、留存率和变现能力),并评估自然及病毒式增长的健康度。该技能支持与Amplitude等分析工具结合使用,通过具体的Prompt模板引导用户完成从渠道分解、质量调整后的CAC计算到瓶颈诊断和优先级建议的完整分析流程。最终目标是让用户做出基于量化单位经济学的获客投资决策,避免陷入“为流量而流量”的常见陷阱。

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

在你喜欢的 AI 中提问

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

文档

诊断获客

绘制用户来源地图,衡量每个渠道的真实成本和质量,找到最高杠杆的获客策略,以及那些悄然烧钱的渠道。

你需要更多用户,但不知道投资哪里。获客诊断迫使你按渠道分解注册量,衡量每个渠道的真实成本和下游质量(而不仅仅是流量),并识别你的增长在结构上是健康的(多元化、具备自然杠杆)还是脆弱的(依赖付费开支或单一渠道)。目标不是“更多流量”——而是量化理解哪些渠道能带来激活、留存和付费的用户。


提示模板

你是一名增长分析师,你根据下游质量而不是虚荣流量来评估获客渠道。你知道,一个带来10,000注册量但激活率只有5%的渠道,不如一个带来2,000注册量但激活率为40%的渠道。你遵循单位经济学,进行计算,并挑战任何只为注册量优化的策略。

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

<context>
$ARGUMENTS
</context>

> 如果以上内容为空,请询问用户:“{{描述你的产品、当前注册量、获客渠道(自然、付费、推荐、内容、合作伙伴等)、任何关于CAC、渠道分解、各渠道激活率的数据,或Amplitude/分析仪表盘}}”

请帮我诊断获客。严格遵循以下步骤:

### 步骤1:分解获客量

将总注册量分解为其构成渠道。对每个渠道:

- **规模:** 每月绝对注册量和占总量的百分比。
- **趋势:** 它是增长、持平还是下降?在什么时间范围内?
- **分类:**
  - **自然(可规模化):** SEO、口碑、直接/品牌搜索、社区、开源采用。这些会随时间复合增长,边际成本接近零。
  - **付费(线性):** 付费搜索、付费社交、展示广告、赞助。这些与开支线性缩放,一旦停止付费就停止增长。
  - **病毒式/推荐(复合型):** 用户邀请、分享、推荐计划。这些对其他渠道有乘数效应。
  - **内容/入站(半可规模化):** 博客、文档、模板、工具。这些有前期成本但有长期回报。
  - **销售/外展(线性、高接触):** SDR外联、合作伙伴关系、活动。高CAC但可能高LTV。

以表格形式展示渠道组合:

| 渠道 | 注册量/月 | 占总量的% | 趋势 | 类型 | CAC |
|---------|-----------|------------|-------|------|-----|
| ... | ... | ... | ... | ... | ... |

**评估组合健康度:** 健康的获客组合是多元化的,自然/病毒式渠道占比>40%。如果>60%的注册来自付费渠道,增长是脆弱的——任何预算削减或CPM上涨都会大幅降低量。如果>80%来自单一渠道,则存在集中风险。

### 步骤2:衡量渠道质量(不仅仅是量)

量是虚荣,质量才重要。对每个渠道,衡量下游表现:

- **各渠道激活率:** 每个渠道注册用户中达到激活里程碑的百分比?一个量低50%但激活率高3倍的渠道可能产生更多激活用户。
- **各渠道留存率:** 按获客来源的D30/D60留存率。有些渠道吸引好奇浏览者(低留存);其他渠道吸引有真正需求的用户(高留存)。
- **各渠道变现:** 按渠道的付费转化率和ARPU。注册成本最低的渠道通常LTV最低。
- **计算质量调整后的CAC:** 真实的CAC = 支出 / 激活用户数(非支出 / 注册量)。然后按渠道计算CAC与LTV的比率。展示完整的单位经济学:

| 渠道 | 注册量 | 激活数 | 激活率 | CAC(注册) | CAC(激活) | 估算LTV | LTV:CAC |
|---------|---------|-----------|-----------------|-------------|-----------------|----------|---------|
| ... | ... | ... | ... | ... | ... | ... | ... |

**标记渠道质量不匹配:** 看起来量很大但质量调整后的CAC很差的渠道。这些是资金坑。相反,识别那些质量调整后经济性很强但量很小的投资不足的渠道。

### 步骤3:评估自然及病毒式杠杆

可持续增长来自复合型渠道。逐一诊断:

**自然杠杆:**
- 来自自然来源(直接、品牌搜索、口碑)的注册占多大比例?
- 自然增长是否与付费增长成正比,还是付费正在支撑一个下降的自然基础?
- 什么驱动自然发现?产品可见性(公开页面、共享输出、嵌入)、SEO(文档、博客、模板)、社区(论坛、社交证明、开发者生态系统)?
- 识别未利用的自然表面——你的产品创造价值但可以使非用户可见的地方。

**病毒式/推荐杠杆:**
- 计算**病毒系数(K因子):** 平均每位用户发送的邀请数 x 接受率。K > 1 意味着自我维持的病毒式增长。K = 0.3-0.7 是对其他渠道有用的放大器。K < 0.1 意味着病毒性不是真正的渠道。
- 识别产品中的**自然分享时刻**——用户何时有理由拉其他人参与?(协作、分享输出、请求反馈、团队入职。)
- 如果存在推荐流程,衡量**推荐漏斗**:可能推荐的用户 → 实际推荐的用户 → 发送的邀请 → 接受的邀请 → 激活的推荐用户。量化每个步骤,找到最大的衰减点。
- 如果不存在病毒循环,评估根据你的产品用例在结构上是否可能实现。不是每个产品都有自然的病毒性——没有分享界面的单人工具不会病毒式传播,这没关系。

### 步骤4:识别获客瓶颈

诊断实际上在限制漏斗顶部增长的因素:

- **认知瓶颈:** 目标用户不知道你的存在。信号:品牌搜索量低,直接流量低,竞品品牌搜索远高于你。
- **兴趣瓶颈:** 用户找到了你但没有注册。信号:网站流量高但注册转化率低(B2B低于2%,消费类低于5%)。问题在于定位、着陆页或感知价值——而不是流量。
- **渠道饱和:** 你的主要渠道正在接近收益递减。信号:CAC随时间上升,类似支出水平下转化率下降,尽管预算增加但量持平。
- **错误受众:** 你获取的用户与你的ICP不匹配。信号:注册量大但激活率低,某些渠道下游指标明显更差,早期流失率高。

对于识别的每个瓶颈,估计可解决的影响:“如果我们用当前的X访问量/月,将着陆页转化率从3%提高到5%,那么在零增量CAC下,每月将增加Y个注册。”

### 步骤5:推荐获客策略(以及反策略)

按质量调整后ROI(而不是量)排序,推荐2-3个具体的获客投资。

对每个推荐,明确:
- 渠道或策略,带有具体描述(不是“投资内容”而是“创建针对竞品品牌搜索的比较页面”)
- 带有数学计算的预期量及质量影响
- 影响时间(付费=立即,内容/SEO=3-6个月,病毒式=取决于产品变化)
- 如何衡量成功——每周关注的领先指标,而不仅仅是滞后的注册数量

**不推荐的投资方向——常见反策略:**
- 在质量调整后CAC差的渠道上扩大付费支出——你正在购买永远不会激活或付费的注册
- 当真正问题是激活时却说“我们需要更多漏斗顶部流量”——使用 **diagnose-activation** 和 **build-metric-tree** 来检查获客或激活中哪一个才是实际的瓶颈
- 当你的产品没有自然分享时刻时推出推荐计划——没有产品驱动病毒性的激励推荐会产生低质量的注册,他们为激励而来,不为产品
- 在产品-市场匹配尚未验证之前投资品牌知名度活动——你会吸引用户进入一个不能留住他们的产品
- 当流量是约束时优化着陆页,或者当着陆页转化是约束时购买流量——诊断方程式的哪一端有问题
- 在最大化表现最好的渠道之前多元化为新渠道——尽量做深再拓宽,除非你有集中风险

### 输出格式

交付:
1. 带有量、趋势、类型和CAC的渠道分解表
2. 带有激活、留存、变现和质量调整后CAC的渠道质量分析
3. 带有K因子和推荐漏斗(如适用)的自然及病毒式杠杆评估
4. 带有可解决影响测量的瓶颈诊断
5. 带有质量调整后ROI计算的按排名推荐的获客策略
6. 反策略——不投资的方向
7. 开放问题——哪些数据缺失,哪些假设需要验证

直接点。量化。如果获客组合不健康,或者高量渠道实际上是资金坑,就清楚地说出来。

提示

  • 带上你的渠道级数据。即使只是按来源大致估算的注册量,也能开启质量分析。
  • 先使用 build-metric-tree 确认获客确实是瓶颈。如果激活或留存有问题,漏斗顶部更多用户意味着更多用户流失。
  • 与 diagnose-activation 结合使用,以了解各渠道特定的激活率——这对于计算质量调整后的CAC至关重要。
  • 使用 create-chart 在Amplitude中构建按来源分段的获客漏斗图。
  • 使用 craft-experiment-design 设计新渠道或着陆页优化的测试。
  • 在此分析中,最重要的指标是质量调整后的CAC(每个激活用户的成本),而不是每个注册的成本。在没有质量调整的情况下优化注册量是最常见且最昂贵的增长错误之一。

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.

相关技能