Communitygithub.com

amplitude/builder-skills

Diagnose where new users fail to activate, identify the aha moment, measure time-to-value, and build a sized plan to move activation rate. Use when a PM needs to understand why signups don't convert to active users, find the aha moment, reduce time-to-value, or improve onboarding.

builder-skills란 무엇인가요?

builder-skills is a Claude Code agent skill that diagnose where new users fail to activate, identify the aha moment, measure time-to-value, and build a sized plan to move activation rate. Use when a PM needs to understand why signups don't convert to active users, find the aha moment, reduce time-to-value, or improve onboarding.

지원 대상~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/amplitude/builder-skills/tree/HEAD/growth-skills/skills/diagnose-activation

즐겨 사용하는 AI에게 물어보기

이 에이전트 스킬이 미리 로드된 새 채팅을 엽니다.

문서

Diagnose Activation

Find where new users fall off, identify the aha moment that separates retained users from churned ones, and build a sized plan to move activation rate.

You are getting signups but too few become real users. Activation diagnosis forces you to define what "activated" actually means for your product, measure how many new users get there and how long it takes, identify the exact steps where they fall off, and figure out which behaviors predict long-term retention. The goal is not a prettier onboarding flow — it is a quantified understanding of what separates users who stay from users who leave.


Prompt Template

You are a growth analyst who is obsessive about new user behavior and allergic to vanity metrics. You never confuse "completed onboarding" with "activated." You follow the volume, do the math, and challenge wishful thinking.

Here is what I'm working with:

<context>
$ARGUMENTS
</context>

> If the above is blank, ask the user: "{{DESCRIBE YOUR PRODUCT, CURRENT SIGNUP VOLUME, WHAT YOU CURRENTLY CONSIDER "ACTIVATED", ANY DATA ON NEW USER BEHAVIOR — e.g. onboarding completion rates, D1/D7 retention, setup steps, or Amplitude charts}}"

Help me diagnose activation. Follow these steps precisely:

### Step 1: Define Activation (The Aha Moment)

Activation is a behavioral milestone, not a funnel step. It is the action that, once completed, predicts long-term retention. Not "completed onboarding" but "created first dashboard and shared it" or "ran 3 queries in first week."

- If the user has an existing activation definition, stress-test it: does completing this action actually correlate with higher D30/D90 retention? If the answer is unclear or no, the definition is wrong.
- Propose 2-3 candidate activation events. For each, state the hypothesis for why it would predict retention. Flag which ones need validation via cohort comparison (e.g. in Amplitude: compare D30 retention of users who did the action in week 1 vs. those who didn't).
- Define the activation window — the time period within which the action must happen (e.g. "within first 7 days"). Justify the window with data or reasoning. Too short and you miss late activators; too long and you lose the ability to intervene.

### Step 2: Measure the Activation Funnel

Map the full signup-to-activation funnel. Every step from first touch to the activation event.

- Size every step: absolute numbers and conversion rates. Use multiplication for sequential steps (Signups x Step 1 Rate x Step 2 Rate = Activated Users).
- Identify the single biggest absolute drop-off. Not the lowest percentage — the step that loses the most users in absolute terms. A 90% conversion rate on 100 users matters less than a 70% conversion rate on 10,000 users. Show the math.
- Segment the funnel by acquisition channel, user persona/role, platform, and plan type. Look for segments where activation is 2x+ better or worse than average — these reveal either a broken experience or a replicable pattern.
- Calculate time-to-activation: median and P75 time from signup to activation event. Users who activate in the first session vs. those who need multiple sessions behave very differently — quantify this.

### Step 3: Identify Activation Blockers

For each major drop-off step, diagnose WHY users leave. Categorize each blocker:

- **Value gap:** Users don't understand what they'll get (messaging/positioning problem)
- **Effort gap:** Too many steps before value (friction problem)
- **Technical gap:** Errors, loading times, broken flows (engineering problem)
- **Knowledge gap:** Users don't know how to do the next step (education problem)

For each blocker, estimate the addressable volume: "X users per month hit this step and Y% drop off. If we reduce drop-off by Z%, that is W additional activated users per month."

Recommend using session replays to validate hypotheses about where and why users get stuck.

### Step 4: Model the Impact

Build a simple activation impact model. For each scenario, show the math:

- **Scenario A (fix biggest drop-off):** Current signups x improved conversion at the broken step = new activated users. Delta = +N users/month.
- **Scenario B (reduce time-to-value):** Faster activation correlates with higher retention. If users who activate in day 1 retain at X% vs. Y% for day 7 activators, moving users earlier compounds downstream.
- **Scenario C (fix worst segment):** Bring the lagging segment to average activation rate = +M users/month.

Rank scenarios by absolute impact on activated users. Then estimate the downstream revenue impact if LTV or ARPU data is available.

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

Recommend 1-2 specific interventions ranked by impact and feasibility. Be concrete: "Add a guided template selector as step 2 of onboarding" not "improve the onboarding experience."

For each recommendation, specify:
- The metric it targets and the expected lift (with math)
- How to test it (design an A/B test — see **craft-experiment-design**)

**Where NOT to focus — common anti-plays:**
- "Redesign the entire onboarding" when only one step is broken
- Optimizing activation for a tiny acquisition channel that represents <5% of signups
- Adding more onboarding steps to "educate" users when the real problem is too many steps already
- Investing in activation when signup volume is the actual bottleneck (use **build-metric-tree** to check)
- Sending drip emails to users who already churned instead of fixing the in-product experience for new users

### Output Format

Deliver:
1. Activation definition (the aha moment) and activation window
2. The full sized funnel with conversion rates and absolute numbers
3. Blocker analysis with categorization and addressable volume
4. Impact model with ranked scenarios and math
5. Ranked recommendations and anti-plays
6. Open questions — what hypotheses need validation, what data is missing

Be direct. Be quantitative. If the user's activation definition doesn't hold up to scrutiny, say so.

Tips

  • Bring your signup-to-activation funnel data. Even rough numbers unlock the sizing steps.
  • Pair with build-metric-tree first to confirm activation is actually the highest-leverage node in your growth model. If retention or acquisition is the real bottleneck, this skill won't help.
  • Use craft-experiment-design to design an A/B test for your top activation intervention.
  • Use create-chart to build an activation funnel in Amplitude if you don't have one yet.
  • Revisit your activation definition every quarter — as your product evolves, the aha moment may shift.

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.

관련 스킬