Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From launch-skills
Writes launch announcement emails, changelog digests, and product update emails for releases. Covers subject lines, tiered structures for full-list blasts, segments, and digests.
npx claudepluginhub amplitude/builder-skills --plugin launch-skillsHow this skill is triggered — by the user, by Claude, or both
Slash command
/launch-skills:launch-emailThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill helps write emails for product launches — from full-list announcements to segmented feature emails to changelog digests. Email consistently outperforms social for conversion because it reaches people who already care. The goal is to leverage that existing relationship: be direct, be valuable, and get the reader to the product fast.
Writes product update emails, feature announcement newsletters, and subscriber digests from marketing briefs, blog posts, changelogs, PRs, git diffs, codebase features, or freeform text.
Use this skill when the user asks to "write a launch announcement", "announce this feature", "write a launch email", "product announcement", "release notes", "launch blog post", "feature announcement to customers", "write the Slack announcement for this launch", or is preparing to communicate a new feature or product to users, customers, or the public.
Generates sequenced multi-email campaigns for onboarding, product launches, lead nurturing, and re-engagement, producing subject lines, preview text, full body copy, CTAs, and send-timing recommendations.
Share bugs, ideas, or general feedback.
This skill helps write emails for product launches — from full-list announcements to segmented feature emails to changelog digests. Email consistently outperforms social for conversion because it reaches people who already care. The goal is to leverage that existing relationship: be direct, be valuable, and get the reader to the product fast.
For major new products or platform shifts. Goes to your entire subscriber list. This is your highest-stakes email — treat it accordingly.
Structure: Subject line → hero (what launched + why it matters) → visual (screenshot or GIF) → 2-3 supporting points → single CTA → signature.
Keep it under 400 words. Email is not a blog post. Link to the landing page and blog post for depth.
For major new features that matter to a specific subset of users. Sends to the relevant segment only — this is both more targeted and protects your full list from email fatigue.
Structure: Subject → direct hook (why this segment should care) → what it does → how to try it → CTA.
Keep it under 300 words. The segment already knows your product; skip the preamble.
For smaller improvements, bundled weekly or biweekly. Goes to users who opt in to changelog updates.
Structure: "[Week of X] — What's new" → short bulleted list of improvements → link to full changelog.
Keep it under 150 words. Brevity signals respect for the reader's time.
The subject line is the tweet first-line equivalent for email. It determines whether the email gets opened.
Most email clients show 40-90 characters of preview text after the subject. Write it intentionally — don't let the email client pull the first line of body copy (often unreadable). The preview text should complement, not repeat, the subject.
Subject: "Introducing real-time translation for voice apps" Preview: "14 languages, sub-200ms latency, available now on free tier"
State what launched and the primary value. No warmup. No "Hope you're having a great week."
Good: "Today we're launching [Feature] — you can now [do specific thing] directly from [product]."
Weak: "We've been working hard on something we're really excited to share with you."
Cover 2-3 supporting points. Each one should answer a reader question:
Use short paragraphs — 2-3 sentences max. Emails with walls of text get skimmed or deleted.
Include a product screenshot, GIF, or short video. Embed it, don't link to it. The visual should show the product doing the thing the opening promises. No stock photos.
One link. Make it a button, not just a hyperlink. Be specific: "Try [Feature] now" beats "Learn more."
Place it prominently after the body — not buried at the bottom after a second screen of text.
Keep it human. A name, role, and optionally a one-liner about what you're building. Avoid legal footers cluttering the main email body (put them in fine print below).
| Scenario | Segment |
|---|---|
| New product, new category | Full list |
| Major feature for power users | Users who use related features |
| Integration with third-party tool | Users who have connected that tool |
| Pricing change | Affected plan tiers only |
| Beta → GA | Users in beta + waitlist |
| Changelog digest | Changelog subscribers only |
Sending to the wrong segment is worse than not sending at all. A power-user feature email sent to inactive free users trains them to ignore your emails.
Email is not the first thing you send on launch day — social is. The sequence:
For Tier 1 launches, send email 2-4 hours after the social posts go out. This staggers your traffic sources and gives you something to say in the email ("Check out the full post →").
The digest is a habit, not an announcement. It rewards users who stay subscribed by showing consistent momentum.
Subject: [Product] updates — week of [date]
What's new this week:
• [Improvement 1] — one sentence on what changed and why it matters
• [Improvement 2] — same
• [Improvement 3] — same
[Optional: one sentence on what's coming next week]
→ Full changelog: [link]
Keep each bullet to one sentence. If an improvement needs more explanation, it probably warrants its own Tier 2 email.
Ship the digest on a consistent day (Friday afternoons work well — it's a low-send-competition window and feels like a weekly wrap-up).