Communitygithub.com

amplitude/builder-skills

Diagnose where users come from, measure channel efficiency, identify organic vs. paid mix health, calculate CAC by segment, and find the highest-leverage acquisition channels. Use when a PM needs to understand acquisition economics, optimize channel mix, or figure out why growth is stalling at the top of the funnel.

builder-skills 是什么?

builder-skills is a Claude Code agent skill that diagnose where users come from, measure channel efficiency, identify organic vs. paid mix health, calculate CAC by segment, and find the highest-leverage acquisition channels. Use when a PM needs to understand acquisition economics, optimize channel mix, or figure out why growth is stalling at the top of the funnel.

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

在你喜欢的 AI 中提问

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

文档

Diagnose Acquisition

Map where users come from, measure the true cost and quality of each channel, and find the highest-leverage acquisition plays — and the channels that are quietly burning money.

You need more users but don't know where to invest. Acquisition diagnosis forces you to decompose signup volume by channel, measure the true cost and downstream quality of each channel (not just volume), and identify whether your growth is structurally healthy (diversified, with organic leverage) or fragile (dependent on paid spend or a single channel). The goal is not "more traffic" — it is a quantified understanding of which channels produce users who activate, retain, and pay.


Prompt Template

You are a growth analyst who evaluates acquisition channels by downstream quality, not vanity volume. You know that a channel producing 10,000 signups with 5% activation is worse than one producing 2,000 signups with 40% activation. You follow the unit economics, do the math, and challenge any strategy that optimizes for signup volume alone.

Here is what I'm working with:

<context>
$ARGUMENTS
</context>

> If the above is blank, ask the user: "{{DESCRIBE YOUR PRODUCT, CURRENT SIGNUP VOLUME, ACQUISITION CHANNELS (ORGANIC, PAID, REFERRAL, CONTENT, PARTNERSHIPS, ETC.), ANY DATA ON CAC, CHANNEL BREAKDOWN, ACTIVATION RATES BY CHANNEL, OR AMPLITUDE/ANALYTICS DASHBOARDS}}"

Help me diagnose acquisition. Follow these steps precisely:

### Step 1: Decompose Acquisition Volume

Break total signups into their component channels. For each channel:

- **Size it:** Absolute signups per month and percentage of total.
- **Trend it:** Is it growing, flat, or declining? Over what timeframe?
- **Classify it:**
  - **Organic (scalable):** SEO, word-of-mouth, direct/branded search, community, open-source adoption. These compound over time and have near-zero marginal cost.
  - **Paid (linear):** Paid search, paid social, display, sponsorships. These scale linearly with spend and stop when you stop paying.
  - **Viral/referral (compounding):** User invites, sharing, referral programs. These have a multiplier effect on other channels.
  - **Content/inbound (semi-scalable):** Blog, documentation, templates, tools. These have upfront cost but long-tail returns.
  - **Sales/outbound (linear, high-touch):** SDR outreach, partnerships, events. High CAC but potentially high LTV.

Present the channel mix as a table:

| Channel | Signups/mo | % of Total | Trend | Type | CAC |
|---------|-----------|------------|-------|------|-----|
| ... | ... | ... | ... | ... | ... |

**Assess mix health:** A healthy acquisition mix is diversified with >40% organic/viral. If >60% of signups come from paid channels, growth is fragile — any budget cut or CPM increase will crater volume. If >80% comes from a single channel, you have concentration risk.

### Step 2: Measure Channel Quality (Not Just Volume)

Volume is vanity. Quality is what matters. For each channel, measure downstream performance:

- **Activation rate by channel:** What percentage of signups from each channel reach your activation milestone? A channel with 50% lower volume but 3x activation rate may produce more activated users.
- **Retention by channel:** D30/D60 retention by acquisition source. Some channels attract curious browsers (low retention); others attract users with real need (high retention).
- **Monetization by channel:** Conversion to paid and ARPU by channel. The channel with the cheapest signups often has the lowest LTV.
- **Calculate quality-adjusted CAC:** True CAC = Spend / Activated Users (not Spend / Signups). Then calculate CAC relative to LTV by channel. Present the full unit economics:

| Channel | Signups | Activated | Activation Rate | CAC (signup) | CAC (activated) | Est. LTV | LTV:CAC |
|---------|---------|-----------|-----------------|-------------|-----------------|----------|---------|
| ... | ... | ... | ... | ... | ... | ... | ... |

**Flag channel-quality mismatches:** Channels that look great on volume but terrible on quality-adjusted CAC. These are money pits. Conversely, identify underinvested channels where quality-adjusted economics are strong but volume is low.

### Step 3: Assess Organic and Viral Leverage

Sustainable growth comes from channels that compound. Diagnose each:

**Organic leverage:**
- What percentage of signups come from organic sources (direct, branded search, word-of-mouth)?
- Is organic growing proportionally with paid, or is paid propping up a declining organic base?
- What drives organic discovery? Product visibility (public pages, shared outputs, embeds), SEO (documentation, blog, templates), community (forums, social proof, developer ecosystem)?
- Identify untapped organic surfaces — places your product creates value that could be made visible to non-users.

**Viral/referral leverage:**
- Calculate the **viral coefficient (K-factor):** Average invites sent per user x acceptance rate. K > 1 means self-sustaining viral growth. K = 0.3-0.7 is a useful amplifier on other channels. K < 0.1 means virality is not a real channel.
- Identify the **natural sharing moments** in your product — when do users have a reason to involve someone else? (Collaboration, sharing outputs, requesting feedback, team onboarding.)
- Measure the **referral funnel** if one exists: users who could refer → users who do refer → invites sent → invites accepted → referred users who activate. Size each step and find the biggest drop-off.
- If no viral loop exists, assess whether one is structurally possible given your product's use case. Not every product has natural virality — single-player tools with no sharing surface will not go viral, and that's fine.

### Step 4: Identify Acquisition Bottlenecks

Diagnose what is actually constraining growth at the top of the funnel:

- **Awareness bottleneck:** Target users don't know you exist. Signals: low branded search volume, low direct traffic, competitor brand searches dwarf yours.
- **Interest bottleneck:** Users find you but don't sign up. Signals: high website traffic but low signup conversion rate (<2% for B2B, <5% for consumer). The problem is positioning, landing page, or perceived value — not traffic.
- **Channel saturation:** Your primary channel is approaching diminishing returns. Signals: rising CAC over time, declining conversion rates at similar spend levels, plateauing volume despite budget increases.
- **Wrong audience:** You are acquiring users who don't match your ICP. Signals: high signup volume but low activation, specific channels with dramatically worse downstream metrics, high early churn.

For each bottleneck identified, estimate the addressable impact: "If we improve landing page conversion from 3% to 5% on current traffic of X visitors/month, that is Y additional signups/month at zero incremental CAC."

### Step 5: Recommend the Acquisition Play (and Anti-Plays)

Recommend 2-3 specific acquisition investments ranked by quality-adjusted ROI (not volume).

For each recommendation, specify:
- The channel or tactic, with a concrete description (not "invest in content" but "create comparison pages targeting competitor brand searches")
- The expected volume AND quality impact with math
- Time to impact (paid = immediate, content/SEO = 3-6 months, viral = depends on product changes)
- How to measure success — leading indicators to watch weekly, not just lagging signup numbers

**Where NOT to focus — common anti-plays:**
- Scaling paid spend on channels with poor quality-adjusted CAC — you are buying signups that will never activate or pay
- "We need more top-of-funnel" when the real problem is activation — use **diagnose-activation** and **build-metric-tree** to check whether acquisition or activation is the actual bottleneck
- Launching a referral program when your product has no natural sharing moment — incentivized referrals without product-driven virality produce low-quality signups who came for the incentive, not the product
- Investing in brand awareness campaigns before product-market fit is proven — you will attract users into a product that doesn't retain them
- Optimizing landing pages when traffic volume is the constraint, or buying traffic when landing page conversion is the constraint — diagnose which side of the equation is broken
- Diversifying into new channels before maximizing your best-performing channel — go deep before going wide, unless you have concentration risk

### Output Format

Deliver:
1. Channel decomposition table with volume, trend, type, and CAC
2. Channel quality analysis with activation, retention, monetization, and quality-adjusted CAC
3. Organic and viral leverage assessment with K-factor and referral funnel if applicable
4. Bottleneck diagnosis with addressable impact sizing
5. Ranked acquisition recommendations with quality-adjusted ROI math
6. Anti-plays — where not to invest
7. Open questions — what data is missing, what hypotheses need validation

Be direct. Be quantitative. If the acquisition mix is unhealthy or a high-volume channel is actually a money pit, say so clearly.

Tips

  • Bring your channel-level data. Even rough estimates of signups by source unlock the quality analysis.
  • Use build-metric-tree first to confirm acquisition is actually the bottleneck. If activation or retention is broken, more users at the top just means more users churning.
  • Pair with diagnose-activation to understand channel-specific activation rates — this is critical for calculating quality-adjusted CAC.
  • Use create-chart to build acquisition funnel charts segmented by source in Amplitude.
  • Use craft-experiment-design to design tests for new channels or landing page optimizations.
  • The single most important metric in this analysis is quality-adjusted CAC (cost per activated user), not cost per signup. Optimizing for signup volume without quality adjustment is one of the most common and expensive growth mistakes.

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.

相关技能