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".

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".

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".

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".

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.

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".

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".

Pre-call intelligence skill that auto-assembles a role-specific brief from multiple data sources so no one walks into a customer call cold. Generates a polished HTML document with company context, stakeholder profiles, pain points, competitive intel, and gap analysis. ALWAYS use this skill when the user mentions: preparing for a call, pre-call prep, call brief, know before you go, customer brief, meeting prep for a prospect or customer, "what do we know about [company]", "brief me on [account]", "get me ready for my call with [company]", deal intel, account intelligence, or show up already knowing. Also trigger when the user asks to generate a demo script and wants account context pulled in first, or when prepping for a QBR, executive briefing, or renewal conversation. Works for both SEs and AEs with role-specific output.

Turn one or more meeting transcripts, notes, or Slack threads into concise takeaways and clear action items with DRIs. Works with a single meeting or a batch from the whole week.

Write a weekly stakeholder update on a core pillar or initiative — metrics, bets in progress, customer quotes, and highlights. Use when you need to keep leadership and cross-functional partners informed on what's shipping and what's moving.

Think 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.

Decompose 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.

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.

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.

Diagnose revenue leaks, analyze willingness-to-pay, evaluate packaging and pricing, and identify expansion revenue opportunities. Use when a PM needs to improve conversion to paid, optimize pricing, reduce revenue churn, or find upsell and expansion opportunities.

Diagnose 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.

Identify, 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.

Write a PR/FAQ for a product idea using Amazon's Working Backwards process. Start from the customer press release and work backward to what needs to be built. Use when validating whether an idea is worth building before committing to a spec.

Take raw user interview notes or feedback and extract themes and insights. Use when synthesizing qualitative data from interviews, surveys, support tickets, or feedback.

Write a hypothesis, define success metrics, and plan a holdout strategy. Use when designing A/B tests or experiment plans.

Summarize experiment results, call a winner, and draft a stakeholder-ready recommendation. Use when an A/B test is complete and you need to communicate results.

Turn 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.

Break a PRD or feature description into implementable user stories with acceptance criteria. Use when handing off to engineering or breaking down work for sprint planning.

Evaluate or develop strategy using Richard Rumelt's kernel of good strategy — Diagnosis, Guiding Policy, and Coherent Actions. Use when you need to cut through vague strategic plans and get to the hard choices, or when you suspect your "strategy" is actually just a list of goals.

Apply Andy Grove's High Output Management principles to diagnose team productivity, design processes, and make management decisions. Use for team structure, meeting design, decision-making, performance management, and operational leverage.

Uncover 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.

Plan and evaluate customer conversations using The Mom Test — ask questions that even your mom can't lie to you about. Use when preparing for user interviews, evaluating research quality, or designing questions that extract real signal instead of polite lies.

Identify 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.

Take 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.

Write 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).

Plan 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.

Write 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.

Design 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.

Set 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.

Plan 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.

Craft 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.

Plan 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.

Design 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.

Define 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.

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.