Communitygithub.com

amplitude/builder-skills

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.

What is builder-skills?

builder-skills is a Claude Code agent skill that 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.

Works with~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/amplitude/builder-skills/tree/HEAD/launch-skills/skills/launch-tweet

Ask in your favorite AI

Open a new chat with this agent skill pre-loaded.

Documentation

Launch Tweet

This skill helps craft social media announcements for product launches. The principles here are platform-aware — what works on X doesn't copy-paste to LinkedIn — but the core goal is the same: stop the scroll, communicate value, and drive action.

Single launch tweet

The single tweet is your most important launch asset. Even if you're doing a full thread, this tweet needs to work on its own because most people will only see it.

Structure

[Strong first line — what you launched, framed as value]

[1-2 sentences expanding on what it does / why it matters]

[Media: video, GIF, or screenshot — attached, not linked]

Rules

  1. First line does all the work. It must make clear you're launching something and why anyone should care. No "excited to announce" or "after months of hard work" — lead with the product value.

  2. Media in the first tweet. Always. A tweet with a video or image gets dramatically more engagement than text alone. Attach the media directly — don't link to YouTube or an external page.

  3. No link in the first tweet. Platform algorithms penalize external links. Put your link in a reply or the second tweet of a thread. If you must include a link and want the preview card to render, keep the entire tweet (including URL) under 280 characters.

  4. Specificity over hype. "Now you can build voice apps in 5 lines of code" beats "Revolutionary new API." Numbers, concrete use cases, and before/after comparisons stop the scroll.

Examples

Good first lines:

  • "Introducing [Product]: [concrete thing it does]"
  • "[Product] now does [specific capability]. Here's what that means →"
  • "You can now [action] with [product]. No [previous friction point] required."
  • "We just shipped [feature]. [One-line proof point or result]."

Weak first lines (avoid):

  • "Excited to announce..." (buries the value)
  • "After months of hard work..." (nobody cares about your timeline)
  • "Thread 🧵" (penalized, provides no value)
  • "Big news!" (empty hype)

Launch threads

Threads work for Tier 1 and some Tier 2 launches where you have enough substance to fill 4-8 tweets without padding.

Thread structure

Tweet 1: The hook Same rules as the single tweet. This must work standalone. Include your best media (video or key screenshot). No link.

Tweets 2-4: Value props and proof Each tweet covers one value prop or proof point. Include supporting media — screenshots, GIFs, short demo clips. Visual breaks every 2-3 tweets keep people scrolling.

Tweet 5-7 (optional): Social proof or use cases Customer quotes, benchmarks, comparisons, example use cases. This is where you make the value concrete.

Final tweet: Call to action + link This is where the link goes. Be specific about what happens when they click: "Try it free →", "See the docs →", "Watch the full demo →".

Thread principles

  • 5-8 tweets is the sweet spot for launch content. Threads over 15 see sharp engagement drop-off.
  • Each tweet must provide value on its own. People drop off at every tweet — don't build toward a punchline at tweet 7.
  • Visual breaks matter. Alternate between text-heavy and media-heavy tweets.
  • No filler tweets. If you can't fill 5 tweets with substance, do a single tweet instead.

Cross-platform adaptation

The same announcement needs different treatment on each platform. Don't just copy-paste.

X/Twitter

  • Concise, punchy, visual-first
  • Thread format for bigger launches
  • Hashtags: use sparingly (1-2 max) or skip entirely
  • Best engagement: mornings and early afternoon (audience-dependent)

LinkedIn

  • Longer-form, more narrative
  • Open with a hook but can be more contextual than X
  • Works well for B2B launches and technical products
  • Include 3-5 line breaks for readability (LinkedIn truncates after ~3 lines, so the first 3 lines must earn the "see more" click)
  • Tag relevant people and companies
  • No hashtag stuffing — 3 max, at the end

BlueSky

  • Similar to X in format and tone
  • Slightly more technical/niche audience (as of 2025-2026)
  • Threads work well here
  • Less algorithmic amplification — rely more on community sharing

Threads

  • More casual, conversational tone
  • Shorter posts tend to work better
  • Cross-posting from Instagram helps distribution
  • Less business/tech-native audience — frame for broader appeal

Hacker News

  • Not a "post" in the social media sense — it's a submission with a title
  • Title should be factual and specific, not hype-y: "Show HN: [Product] – [what it does in plain terms]"
  • The discussion thread matters more than the submission itself
  • Be ready to answer technical questions honestly and in detail
  • Don't ask people to upvote — it will backfire

Writing process

When drafting launch social copy, follow this sequence:

  1. Start with the messaging brief (from launch-strategy). If there's no brief, ask for: product/feature name, target audience, primary value prop, and 2-3 secondary value props.

  2. Write the X/Twitter version first. The character constraint forces clarity. If the value prop doesn't fit in a tweet, the messaging isn't sharp enough.

  3. Expand to a thread if the launch warrants it (Tier 1 or substantial Tier 2). Map each secondary value prop to a tweet.

  4. Adapt for other platforms. LinkedIn gets more context and narrative. BlueSky stays concise. Hacker News gets a factual title.

  5. Draft multiple first-line options. The first line is the highest-leverage sentence. Write 3-5 variants and pick the one that best balances clarity, specificity, and scroll-stopping power.

Common mistakes

  • Linking in the first tweet. It tanks reach. Always put links in a reply or later in the thread.
  • No media. Text-only launch tweets underperform dramatically. Even a screenshot is better than nothing.
  • Burying the value. Three sentences of preamble before saying what you launched. Lead with the product.
  • Same copy everywhere. Each platform has different norms. Copy-paste looks lazy and performs poorly.
  • Thread padding. If you're adding tweets just to make the thread longer, cut them. Short and strong beats long and diluted.
  • Forgetting the CTA. Every launch post needs a clear next step for the reader. What do you want them to do?

Companion skills

  • launch-strategy — messaging brief that feeds the social copy
  • launch-email — email subject lines follow the same "first line" craft as tweets
  • launch-video — the demo video or GIF that goes in the tweet (attached, not linked)
  • launch-distribution — when and where to post, and how to amplify
  • launch-metrics — track which social posts drive signups via UTMs

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.

Related Skills