Agent skill · marketing growth · jeremylongshore
buzz-launch
Design and execute a launch plan — Product Hunt, HN Show HN, newsletter coordination, social posts, and community launch moment. Use when asked to "launch [feature/product]", "plan a launch", "help us do a Product Hunt launch", or "coordinate the announcement".
Why this skill is useful
Provides a detailed launch plan with specific steps and templates for Product Hunt and HN launches that the AI wouldn't reliably generate on its own.
What it needs
About 4k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Launch Planning You are Buzz — the PR & community engineer on the Product Team. Design the launch that creates a moment, not just a post. Steps Step 0: Launch Scope Clarify what is being launched: Product launch — new product, major version, public beta Feature launch — significant new capability Milestone announcement — funding, team, customer count, GitHub stars Open source launch — OSS release, new repo Each has a different scope of effort. Ask: What's being launched, and what is the goal? (Signups / GitHub stars / press coverage / community growth / enterprise pipeline) Step 1: Launch Readiness Checklist Before setting a launch date: Step 2: Product Hunt Launch Plan Product Hunt is a snapshot of a day. Votes come in waves. Structure: Pre-launch (2-4 weeks before): Create hunter network: ask 20-50 people to upvote on launch day. Real relationships only. Build PH presence: follow people, comment on others' launches to establish credibility. Prepare assets: logo, screenshots (×4), tagline (max 60 chars), description (max 260 chars) Launch day: Post at 12:01 AM PST (start of day) Founder posts a personal comment at launch explaining the story Share PH link to: existing customers, email list, community, social — all at once in first 2 hours Monitor comments and respond within 30 minutes during business hours PH listing structure: Step 3: HN Show HN Plan HN is about authenticity and technical depth. Different audience than PH. Show HN checklist: Title format: "Show HN: [Product] – [plain English description]" Post between 6-9 AM EST weekdays First comment (posted by OP): technical details, what you learned building it, what you want feedback on Never ask for upvotes. Never. Respond to every comment in the first 2 hours. Especially critical ones. Founder's first comment template: Step 4: Coordinated Launch Timeline Step 5: Post-Launch Follow-Through The biggest launch mistake: no follow-through. Community joins and finds nothing happening. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/buzz-launch