amplitude
- 168 skills
- 0 followers
- 163 repo stars
- last month last updated
- ▌ Taxonomy 3 · amplitudeSource of truth for event taxonomy generation, data auditing, and governance best practices in Amplitude. Use when an agent needs to create, validate, audit, score, or recommend improvements to event tracking plans, naming conventions, property standards, data quality, or deprecation workflows. Covers naming rules, property standards, scoring frameworks, safe metadata operations, deprecation procedures, and AI readiness guidance.
- ▌ Analyze Experiments 4 · amplitudeAnalyze Amplitude experiments and feature flags through the Amplitude MCP server — inspect experiment setups, evaluate A/B test results and statistical significance, and review feature flag configurations and rollouts. Use when the user asks about an A/B test, experiment results, which variant is winning, statistical significance, feature flag status, rollout percentages, or wants to connect a flag key in code to its Amplitude configuration.
- ▌ Taxonomy 2 · amplitudeSource of truth for event taxonomy generation, data auditing, and governance best practices in Amplitude. Use when an agent needs to create, validate, audit, score, or recommend improvements to event tracking plans, naming conventions, property standards, data quality, or deprecation workflows. Covers naming rules, property standards, scoring frameworks, safe metadata operations, deprecation procedures, and AI readiness guidance.
- ▌ Instrument Events 3 · amplitude bundleGiven event_candidates YAML (output from discover-event-surfaces), generates a concrete instrumentation plan for priority-3 (critical) events. Acts as a Software Architect: discovers existing analytics patterns in the codebase, reads the hinted files to determine what variables are in scope, designs minimal chart-useful properties, and identifies the exact insertion point for each tracking call. Outputs a structured JSON trackingPlan. Use this as step 3 of the analytics instrumentation workflow, after discover-event-surfaces. Trigger whenever a user has event_candidates and wants to generate tracking code, asks "instrument these events", "generate tracking plan", "add analytics for these events", "where should I put the tracking calls", or any request to turn event candidates into concrete implementation guidance.
- ▌ Discover Event Surfaces 3 · amplitude bundleGiven a change_brief YAML (output from diff-intake), generates an exhaustive list of candidate analytics events to instrument. Takes the perspective of an engineer with a PM mindset — surfaces everything worth considering so a PM can decide what actually matters. Use this as step 2 of the analytics instrumentation workflow, immediately after diff-intake produces a change_brief. Trigger whenever a user has a change_brief YAML and wants to know what analytics events to add, or asks "what should I track for this PR", "what events should I instrument", "generate event candidates", or any request to surface analytics coverage gaps for a code change.
- ▌ Discover Analytics Patterns 3 · amplitudeDiscovers how analytics tracking calls are actually written in this codebase — the concrete SDK calls, function signatures, and import patterns used to send events. Use this skill whenever you need to understand the existing analytics instrumentation patterns before adding new tracking, when someone asks "how do we track events here?", "show me the analytics setup", "what's the analytics pattern in this codebase?", or any time the instrument-events or discover-event-surfaces skills are about to run and you need to know the correct coding style to follow. Outputs a deduplicated list of patterns with generalized examples and the file paths where each pattern appears, plus the dominant event and property naming conventions inferred from those call sites. Always use this skill before writing any analytics instrumentation code.
- ▌ Create Chart 3 · amplitudeCreates 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.
- ▌ Analyze Chart 3 · amplitudePerforms 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.
- ▌ Analyze Feedback 3 · amplitudeSynthesizes 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.
- ▌ Create Dashboard 3 · amplitudeBuilds 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.
- ▌ Analyze Dashboard 3 · amplitudeDeeply analyze Amplitude dashboards by analyzing key charts, surfacing top areas for concern and takeaways, identify anomalies, then explain changes using customer feedback trends.
- ▌ Analyze Experiments 3 · amplitudeDesigns 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.
- ▌ Monitor Experiments 3 · amplitude bundleMonitors 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.
- ▌ Analyze Account Health 3 · amplitudeSummarizes 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.
- ▌ Daily Brief 2 · amplitudeDelivers a daily briefing of the most important changes across your Amplitude instance. Use when the user asks for a "daily download", "morning briefing", "what's happening", "anything I should know", or wants a summary of recent metric changes, experiments, and user feedback.
- ▌ Create Chart 2 · amplitudeCreates 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.
- ▌ Debug Replay 2 · amplitudeTurns bug reports into reproducible steps by finding error sessions in Amplitude Session Replay, extracting interaction timelines, and identifying the common action sequence that precedes the failure. Use when a user reports a bug, an error event spikes, someone says "how do I reproduce this", "what happened to user X", "repro steps", or you need to understand what a user did before an error occurred.
- ▌ Weekly Brief 2 · amplitudeDelivers a weekly briefing summarizing the most important trends, wins, and risks across your Amplitude instance. Use when the user asks for a "weekly review", "weekly summary", "week in review", "what happened this week", or wants a recap of the past 7 days to share with their team or leadership.
- ▌ Analyze Chart 2 · amplitudePerforms 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.
- ▌ Diagnose Errors 2 · amplitudeInvestigates errors across network failures, JavaScript errors, and error clicks to identify what's broken, where, and why. Use when the user says "what's broken", "errors are up", "why are users seeing errors", "JS errors", "network failures", "5xx spike", "something is broken", or wants to triage product reliability issues.
- ▌ Replay UX Audit 2 · amplitudeFinds and analyzes Amplitude Session Replays to surface UX friction patterns across multiple sessions. Produces a ranked friction map showing where users struggle, hesitate, or abandon. Use when a PM or designer asks "where's the friction", "what's confusing users", "UX issues on this page", "why is this flow clunky", "audit the user experience", or wants qualitative evidence of usability problems in a specific feature or flow.
- ▌ Analyze Feedback 2 · amplitudeSynthesizes 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.
- ▌ Create Dashboard 2 · amplitudeBuilds 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.
- ▌ Analyze AI Topics 2 · amplitudeAnalyzes what users ask AI agents about and how well each topic is served. Only use when the user has Amplitude Agent Analytics instrumented in their project. Use when the user asks "what are people asking the AI", "top AI topics", "where is the AI struggling", "AI coverage gaps", "what should we improve in our AI", or wants product insights from AI conversation patterns.
- ▌ Analyze Dashboard 2 · amplitudeDeeply analyze Amplitude dashboards by analyzing key charts, surfacing top areas for concern and takeaways, identify anomalies, then explain changes using customer feedback trends
- ▌ Instrument Events 2 · amplitudeGiven event_candidates YAML (output from discover-event-surfaces), generates a concrete instrumentation plan for priority-3 (critical) events. Acts as a Software Architect: discovers existing analytics patterns in the codebase, reads the hinted files to determine what variables are in scope, designs minimal chart-useful properties, and identifies the exact insertion point for each tracking call. Outputs a structured JSON trackingPlan. Use this as step 3 of the analytics instrumentation workflow, after discover-event-surfaces. Trigger whenever a user has event_candidates and wants to generate tracking code, asks "instrument these events", "generate tracking plan", "add analytics for these events", "where should I put the tracking calls", or any request to turn event candidates into concrete implementation guidance.
- ▌ Analyze Experiments 2 · amplitudeDesigns 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.
- ▌ Monitor AI Quality 2 · amplitudeMonitors AI agent health across quality, cost, performance, and errors. Only use when the user has Amplitude Agent Analytics instrumented in their project. Use when the user asks "how are our AI agents doing", "AI quality check", "agent health", "AI errors", "agent performance", "LLM cost", or wants a proactive health report on their AI/LLM features.
- ▌ Monitor Experiments 2 · amplitude bundleMonitors 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.
- ▌ Monitor Reliability 2 · amplitudeDelivers a reliability health check using auto-captured network request, JS error, and error click data. Use when the user asks for a "reliability check", "error rate", "quality metrics", "page health", "did the release break anything", "error budget", or wants a proactive product quality report.
- ▌ Compare User Journeys 2 · amplitudeCompares how two user groups behave differently by analyzing Amplitude Session Replays and metrics side by side. Produces a behavioral diff showing what one group does that the other doesn't. Use when a PM or growth lead asks "what do converters do differently", "how do power users behave", "why do churned users leave", "compare these cohorts", "what separates segment A from B", or wants to understand the qualitative behavioral gap between two user populations.
- ▌ Review Agent Insights 2 · amplitudeRetrieves, synthesizes, and prioritizes all recent AI agent results from Amplitude. Queries every agent type available in get_agent_results, validates freshness, and produces a unified narrative ranked by impact. Use when the user asks "what has the AI found", "show me agent insights", "any AI findings", "what did Amplitude discover", "review AI insights", or wants a digest of everything Amplitude's AI agents have surfaced recently.
- ▌ Analyze Account Health 2 · amplitudeSummarizes 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.
- ▌ Discover Opportunities 2 · amplitudeDiscovers product opportunities by analyzing Amplitude analytics, experiments, session replays, and customer feedback. Synthesizes evidence into prioritized, actionable opportunities with RICE scoring. Use when the user asks to "find opportunities", "what should we build", "where are we losing users", "product gaps", or wants a data-driven backlog of improvements.
- ▌ Investigate AI Session 2 · amplitudeDeep-dives into specific AI agent sessions or failure patterns to explain why something went wrong. Only use when the user has Amplitude Agent Analytics instrumented in their project. Use when investigating a specific session ID, debugging agent failures, understanding why quality is low, tracing tool errors, or when monitor-ai-quality surfaces an issue that needs root cause analysis.
- ▌ Discover Event Surfaces 2 · amplitudeGiven a change_brief YAML (output from diff-intake), generates an exhaustive list of candidate analytics events to instrument. Takes the perspective of an engineer with a PM mindset — surfaces everything worth considering so a PM can decide what actually matters. Use this as step 2 of the analytics instrumentation workflow, immediately after diff-intake produces a change_brief. Trigger whenever a user has a change_brief YAML and wants to know what analytics events to add, or asks "what should I track for this PR", "what events should I instrument", "generate event candidates", or any request to surface analytics coverage gaps for a code change.
- ▌ Discover Analytics Patterns 2 · amplitudeDiscovers how analytics tracking calls are actually written in this codebase — the concrete SDK calls, function signatures, and import patterns used to send events. Use this skill whenever you need to understand the existing analytics instrumentation patterns before adding new tracking, when someone asks "how do we track events here?", "show me the analytics setup", "what's the analytics pattern in this codebase?", or any time the instrument-events or discover-event-surfaces skills are about to run and you need to know the correct coding style to follow. Outputs a deduplicated list of patterns with generalized examples and the file paths where each pattern appears, plus the dominant event and property naming conventions inferred from those call sites. Always use this skill before writing any analytics instrumentation code.
- ▌ Add Analytics Instrumentation 2 · amplitudeEnd-to-end analytics instrumentation workflow for a PR, branch, file, directory, or feature. Reads the code, discovers what events should be tracked, and produces a concrete instrumentation plan — all in one shot. Use this skill whenever a user wants to add analytics to a PR, asks "instrument this PR", "add tracking to this branch", "what analytics does this file need", "instrument the checkout flow", "run the full instrumentation workflow", or any request that implies going from code changes to a tracking plan. Also trigger when the user gives you a PR link, branch name, file path, or feature description and mentions analytics, events, or instrumentation. This is the main entry point for the analytics workflow — prefer it over calling the individual steps (diff-intake, discover-event-surfaces, instrument-events) separately.
- ▌ Instrument With Amplitude AI · amplitudeAuto-instrument a JS/TS AI app with @amplitude/ai. Detects framework, discovers agents and LLM call sites, applies instrumentation, and verifies with tests.
- ▌ Query Analytics · amplitudeQuery Amplitude product analytics through the Amplitude MCP server — find and read charts, dashboards, and notebooks, run metric and dataset queries, and search session replays. Use when the user asks about user behavior, active users, conversion, funnels, retention, engagement, event volumes, a specific Amplitude chart or dashboard, or wants to find session recordings.
- ▌ Instrument Analytics · amplitudeInstrument applications with Amplitude Analytics SDKs — install and initialize the Browser, Node.js, or Python SDK, track events with a clean taxonomy, identify users, enable autocapture and Session Replay, and validate that events arrive. Use when the user wants to add Amplitude to an app, track an event, set user properties, set up session replay, fix events that aren't showing up, or audit existing tracking code.
- ▌ Amplitude Setup · amplitude bundleSet up Amplitude analytics in this codebase using the Amplitude Wizard agent contract. Use whenever a user asks to install Amplitude, instrument analytics events, configure Amplitude SDK, connect this app to Amplitude, or wire up tracking with @amplitude/wizard.
- ▌ Integration Expo · amplitude bundleAmplitude integration for Expo applications using @amplitude/analytics-react-native
- ▌ Integration Ruby · amplitude bundleAmplitude integration for any Ruby application using the amplitude-api gem
- ▌
- ▌ Integration Swift · amplitude bundleAmplitude integration for Swift iOS and macOS applications using AmplitudeSwift
- ▌
- ▌
- ▌
- ▌ Integration Python · amplitude bundleAmplitude integration for any Python application using the amplitude-analytics package
- ▌ Integration Android · amplitude bundleAmplitude integration for Android applications using the Kotlin SDK
- ▌
- ▌
- ▌
- ▌ Wizard Prompt Supplement · amplitude bundleLong-form wizard contracts moved out of the always-on system commandments to keep per-turn prompts small. Load when wiring API keys, before confirm_event_plan, when writing the post-instrumentation events manifest or setup report, or when generating browser SDK init. Pre-staged at .claude/skills/wizard-prompt-supplement/ — use Read on the reference files listed below; do not skip relevant sections for your current phase.
- ▌
- ▌ Integration Astro Ssr · amplitude bundleAmplitude integration for server-rendered Astro applications with API routes
- ▌
- ▌ Integration React Vite · amplitude bundleAmplitude integration for React applications built with Vite (no router)
- ▌ Integration Astro Hybrid · amplitude bundleAmplitude integration for Astro hybrid rendering with both static and server-rendered pages
- ▌
- ▌ Integration React Native · amplitude bundleAmplitude integration for React Native applications using @amplitude/analytics-react-native
- ▌
- ▌ Integration Javascript Web · amplitude bundleAmplitude integration for client-side web JavaScript applications using @amplitude/unified (or @amplitude/analytics-browser for existing projects)
- ▌ Integration Tanstack Start · amplitude bundleAmplitude integration for TanStack Start full-stack applications
- ▌ Integration Javascript Node · amplitude bundleAmplitude integration for server-side Node.js applications using @amplitude/analytics-node
- ▌ Amplitude Chart Dashboard Plan · amplitudeAmplitude Chart & Dashboard Planning Skill — expert implementation strategist for translating an instrumented event taxonomy into a focused set of Amplitude charts and a single well-organized product dashboard. Use after event instrumentation is complete (SDK installed, events implemented, .amplitude/events.json written). Produces a concrete chart plan and drives chart + dashboard creation via the Amplitude MCP.
- ▌ Integration Nextjs App Router · amplitude bundleAmplitude integration for Next.js App Router applications
- ▌ Integration Nextjs Pages Router · amplitude bundleAmplitude integration for Next.js Pages Router applications
- ▌ Integration React React Router 6 · amplitude bundleAmplitude integration for React Router v6 applications
- ▌ Amplitude Quickstart Taxonomy Agent · amplitudeAmplitude Quickstart Taxonomy Agent — expert implementation strategist for a "starter kit" tracking plan: 10–30 high-signal events and properties from URL(s), codebase, and user context. Use when naming events, scoping instrumentation, mapping funnels, or producing a JSON taxonomy aligned to Amplitude analysis (funnels, retention, journeys, group analytics). In the wizard, pair with instrumentation skills; there is no Langley web-crawl stack — gather context with Read/Grep/Glob, WebFetch when available, Amplitude MCP get_context, and the user's free-text goals.
- ▌ Integration Astro View Transitions · amplitude bundleAmplitude integration for Astro with ClientRouter view transitions
- ▌ Integration React React Router 7 Data · amplitude bundleAmplitude integration for React Router v7 - Data mode applications
- ▌ Integration React React Router 7 Framework · amplitude bundleAmplitude integration for React Router v7 - Framework mode applications
- ▌ Integration React React Router 7 Declarative · amplitude bundleAmplitude integration for React Router v7 - Declarative mode applications
- ▌ Integration React Tanstack Router Code Based · amplitude bundleAmplitude integration for React applications using TanStack Router with code-based routing
- ▌ Integration React Tanstack Router File Based · amplitude bundleAmplitude integration for React applications using TanStack Router with file-based routing
- ▌ Yes And · amplitudeThink bigger about your idea while solving the real risks. Inspired by how the best startup advisors give feedback — they find the kernel of something great, push you to see the larger version you're missing, then help you defuse the landmines between here and there.
- ▌ Craft Spec · amplitudeTurn messy ideas into a clear, structured PRD. Use when you have rough notes, Slack threads, or half-formed ideas that need to become a product requirements document.
- ▌
- ▌ Pre Mortem · amplitudeIdentify what could go wrong before launch by imagining failure and working backward. Use after a spec is approved but before you ship — surfaces risks the team isn't talking about.
- ▌ Prioritize · amplitudeTake a list of ideas, features, or initiatives and quickly prioritize them using an effective framework. Use when you have too many things and need to decide what to do first.
- ▌ Launch Email · amplitudeWrite launch announcement emails and changelog digests for product releases. Use this skill whenever someone asks to write a launch email, draft an announcement email, create a product update email, write a changelog digest, or compose an email to accompany a product launch. Also trigger for "write the email for this launch," "draft the announcement email," "help me email our users about this," or any request to craft email copy tied to a product ship. Covers subject lines, announcement structure, segment-specific emails, changelog digests, and timing relative to social.
- ▌ Launch Tweet · amplitudeCraft launch tweets, announcement threads, and social posts for product launches across X/Twitter, LinkedIn, BlueSky, and Threads. Use this skill whenever someone asks to write a launch tweet, draft an announcement thread, create social copy for a product release, or repurpose launch messaging for different platforms. Also trigger for "write the tweet for this launch," "help me announce this on Twitter/X," "draft a LinkedIn post for our new feature," or any request to write social media content tied to a product ship. Handles single tweets, multi-tweet threads, and cross-platform adaptation.
- ▌ Launch Video · amplitudePlan and produce video and visual assets for product launches — demo videos, GIFs, screenshots, and programmatic video with Remotion. Use this skill whenever someone asks to create a demo video, record a product walkthrough, make a launch GIF, plan visual assets for a launch, or decide what media to create for an announcement. Also trigger for "what should our demo video show," "how do we record the product," "I need visuals for the launch," "make a video for this launch," or any request about creating non-text media tied to a product release. Covers video scripting, recording, programmatic video (Remotion), GIF creation, screenshot best practices, and per-platform format guidance.
- ▌ Launch Metrics · amplitudeSet up measurement and tracking for product launches, run post-launch retros with data, and build a launch analytics system. Use this skill whenever someone asks to track a launch, set up UTM parameters, measure launch performance, run a launch retro, analyze launch results, or build a dashboard for a product release. Also trigger for "how do we know if the launch worked," "what should we track for this launch," "set up UTMs for the announcement," or any request about measuring or evaluating a product launch. Covers pre-launch tracking setup, UTM conventions, per-tier KPIs, benchmark expectations, and retro frameworks.
- ▌ Launch Strategy · amplitudePlan and execute product launches using a tiered framework — from major new products down to small improvements. Use this skill whenever someone asks to plan a launch, create a launch checklist, define launch tiers, write launch messaging, or coordinate a product release. Also trigger when someone says "we're launching X" or "how should we announce this feature" or "what's our launch plan" — even if they don't use the word "strategy." Covers messaging, naming, launch assets, timelines, and post-launch retros. This is the master launch skill; it references the companion skills (launch-tweet, launch-landing-page, launch-distribution, launch-email, launch-video, launch-metrics) for specific execution.
- ▌ Playing To Win · amplitude bundleDevelop a strategy using the Playing to Win cascade — Winning Aspiration, Where to Play, How to Win, Capabilities, and Management Systems. Use when you need to make strategic choices about markets, positioning, and competitive advantage.
- ▌ Map Growth Loops · amplitudeIdentify, map, and measure the self-reinforcing growth loops in your product — viral, content, paid, and usage loops. Understand cycle time, throughput, and where loops are broken. Use when a PM needs to move beyond linear funnel thinking and understand the compounding systems that drive sustainable growth.
- ▌ Launch Blog Post · amplitudeWrite technical launch blog posts optimized for both traditional SEO and AI engine citation (AEO). Use this skill whenever someone asks to write a launch announcement blog post, a technical blog post for a product release, a changelog-style post, or any written content tied to a product launch that lives on a blog or docs site. Also trigger for "write the blog post for this launch," "draft the announcement," "I need a technical write-up for this feature," or any request to create long-form launch content. Covers post structure, technical writing, benchmarks, tutorials, SEO, and answer engine optimization (AEO/GEO).
- ▌ Jobs To Be Done · amplitudeUncover the functional, social, and emotional jobs driving customer behavior. Use when you need to understand why customers hire, switch, or abandon products — not just what they say they want.
- ▌ Build Metric Tree · amplitudeDecompose a top-line metric into a quantified metric tree with mathematical relationships, size each node, and identify where the real leverage is. Use when a PM needs to understand what drives a metric, where to focus, or where NOT to focus.
- ▌ North Star Metric · amplitudeDefine a North Star Metric and its input metrics. Classify the game your product plays, evaluate candidates against quality criteria, and build a connected metric system. Use when choosing a North Star, evaluating an existing one, or setting up a metrics framework.
- ▌ Instrument Pr · amplitudeInstruments 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".
- ▌ Pm Weekly Brief · amplitudeRead your Slack mentions, calendar events, and recently modified Drive documents from the last 7 days and synthesize them into a short personal PM summary. Use at the end of each week to capture what happened before it fades.
- ▌ Build Plg Strategy · amplitudeDesign a product-led growth strategy for your product — classify your PLG motion, define activation and monetization architecture, choose distribution channels, plan the PLG-to-sales bridge, and build defensibility. Incorporates AI-era shifts in distribution, pricing, and user expectations. Use when building or overhauling a growth strategy.
- ▌ Diagnose Retention · amplitudeDiagnose where and why users churn, identify natural usage frequency, build cohort retention curves, and find the behaviors that drive long-term retention. Use when a PM needs to understand churn, improve retention curves, or identify what makes users stick.
- ▌ Diagnose Activation · amplitudeDiagnose 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.
- ▌ Launch Distribution · amplitudePlan and execute multi-channel distribution for product launches across X/Twitter, Reddit, LinkedIn, Hacker News, and other platforms. Use this skill whenever someone asks to create a distribution plan, figure out where to post a launch, build a press list, set up internal amplification, or coordinate multi-channel promotion. Also trigger for "where should we post this," "how do we get the word out," or any request about promoting or distributing a product announcement. Covers channel strategy (with deep playbooks for Twitter, Reddit, and LinkedIn), post-launch retro, and building a repeatable distribution engine.
- ▌ Launch Landing Page · amplitudeDesign and build launch landing pages that convert visitors into users. Use this skill whenever someone asks to create a landing page for a product launch, build a feature page, design a signup page, or structure a product marketing page. Also trigger for "make a page for this launch," "I need a landing page," "help me design the product page," or any request to create a web page tied to a product release or feature announcement. Covers page structure, hero design, SEO integration, developer-first patterns, urgency mechanics, waitlist flows, and conversion optimization.