Plans and executes multi-channel product launch distribution across X/Twitter, Reddit, LinkedIn, Hacker News. Provides channel playbooks, press lists, amplification strategies, post-launch retros, and repeatable systems.
From launch-skillsnpx claudepluginhub amplitude/builder-skills --plugin launch-skillsThis skill uses the workspace's default tool permissions.
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Calculates TAM/SAM/SOM using top-down, bottom-up, and value theory methodologies for market sizing, revenue estimation, and startup validation.
This skill covers the "where and how" of getting your launch in front of people. Great messaging and assets are wasted without distribution. The goal isn't to be everywhere — it's to be effective everywhere you show up, and to build a repeatable system that gets better with each launch.
Two principles:
Go wide, then double down. Post to every relevant channel on launch day. You won't know in advance which one will hit. After the launch, look at the data and invest more in what worked.
Launch is day one, not the whole story. The initial push drives awareness, but the long tail — SEO, word of mouth, community — drives sustained growth. Distribution planning should account for both.
The three highest-ROI channels for most product launches are X/Twitter, Reddit, and LinkedIn. Master these first, then layer on additional channels.
X is the default launch channel for tech products. It's where the initial wave of awareness starts, and strong performance here cascades into other channels (people screenshot tweets for LinkedIn, link to threads on Reddit, etc.).
Timing and mechanics:
Maximizing reach:
See launch-tweet skill for crafting the actual posts (first line hooks, thread structure, media rules).
Reddit is underrated for launches. The discussion quality is high, the audience is technical and opinionated, and a good Reddit post has a much longer shelf life than a tweet. Subreddit posts surface in search results for months.
Finding the right subreddits:
Post framing:
Engagement:
LinkedIn is the highest-performing channel for B2B and enterprise product launches. The audience is buying-decision-makers, and the organic reach for strong posts is remarkably high compared to other platforms.
Amplification mechanics:
See launch-tweet skill for LinkedIn post format, hook structure, and tone.
BlueSky / Threads — Smaller audiences but growing. Lower competition means higher visibility per post. Worth posting to — minimal effort, occasional outsized results.
Product Hunt — PH can drive 1,000+ visitors in 24 hours and provide useful social proof (badges, rankings). However, the editorial team now manually curates the homepage, making success less predictable. AI products face extra scrutiny. Budget 50-120 hours for a serious PH launch, so it's best reserved for Tier 1 moments when you have the bandwidth. If you do launch: Tuesday or Wednesday at 12 AM PST, respond to every comment, and don't ask for upvotes directly.
Email — Tier 1: full list announcement. Tier 2: segmented to relevant users. Tier 3: include in changelog digest. Send emails after social posts (gives social a head start on engagement). See launch-email skill for subject lines, structure, and segmentation.
Press and journalists — Only for Tier 1 launches. Build your own contact list over time. Reach out 1-2 weeks before launch with an exclusive or early look. Give journalists data, trend context, or a contrarian take — not just a press release. Don't expect coverage; press is a bonus, not a distribution strategy.
Blog / content — Publish a blog post for Tier 1 and Tier 2 launches (see launch-blog-post skill). Cross-post or syndicate to dev.to, Medium, Hashnode for technical products. Include a tutorial within the first week. Link from docs to the blog post and vice versa.
This is the most underused distribution lever. Your team has a collective social reach that likely exceeds your company account.
Create a dedicated Slack/Teams channel where you post launch assets and copy that team members can share on their personal accounts. Make it easy:
The #amplify channel only works if leadership uses it and participation is normalized. It shouldn't feel like an obligation — frame it as "here's something cool we shipped, help us get the word out." Celebrate team members who drive engagement.
For Tier 1 launches, personally reach out to 10-20 people with relevant audiences and ask for a reshare. These should be genuine connections, not cold outreach. A quote-tweet with personal commentary from someone respected in your space is worth more than 100 company retweets.
On launch day, timing matters. Here's a typical sequence:
Early morning (6-8 AM, audience timezone):
Mid-morning (9-11 AM):
Late morning / early afternoon:
Throughout the day:
Run the retro within a week of launch (see launch-strategy for the full retro framework). For distribution specifically, capture:
Update your distribution checklist based on findings. The goal is to make each launch easier and more effective than the last.
Distribution isn't a one-time plan — it's a system. Over successive launches:
The best distribution is a habit, not a heroic effort.