Install any skill in seconds. Free to start, no credit card required.
Get Started Free →kostja94/product-hunt-launch
When the user wants to launch on Product Hunt, prepare a PH submission, or plan launch day (hunter, first comment, timing, upvotes). Also use when the user mentions "Product Hunt," "launch on Product Hunt," "PH launch," "Product Hunt submission," "hunter," "Product of the Day," "upvotes," or "Product Hunt first comment." For multi-platform directory listings and paste-ready copy beyond PH, use directory-submission.
Passed 18 of 22 test cases with the skill, and 15 of 22 without it.
and 1 more in the full report
4 fixed14 passed either way3 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
One of 4 test cases the skill fixed. Same model, same prompt, with and without the skill.
I am drafting a Product Hunt submission for my developer tool CodeSprint. I want a high-energy tagline with emojis: '🚀 Skyrocket your API build speeds in minutes with instant TypeScript mocks! 🔥'. Please refine this into compliant tagline options.
| Checked | Without skill | With skill |
|---|---|---|
| Proposed tagline options are strictly 60 characters or shorter. | Passed | Passed |
| Proposed tagline options omit decorative emojis. | Missed | Passed |
The instructions your model reads when the skill loads.
Guides preparing and executing a Product Hunt launch. Product Hunt is a community-driven product discovery platform; only ~10% of submissions get featured on the homepage. Best for SaaS, developer tools, AI/ML products, and productivity software. Physical products and service businesses have limited success.
When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.
Project context: Read root contextus.md when present and load only the modules relevant to this task. Without Contextus, use available project material or user-provided facts and ask for missing information; do not create a parallel context system.
Identify:
| Phase | Days | Actions |
|---|---|---|
| Teaser | 30–21 | Build "notify me" page; decide self-hunt vs hunter; engage in community |
| Supporters | 20–11 | Build list of 200+ (makers, industry contacts, followers, users) |
| Assets | 10–3 | Finalize tagline (≤60 chars), gallery images (1270×760), demo video (<2 min), maker comment, 3–5 topic tags; build awareness on X/LinkedIn 2–4 weeks before |
| Launch day | 2–1 | Clear calendar for 16+ hours; Product Hunt runs midnight–midnight Pacific |
| Field | Spec |
|---|---|
| Tagline | ≤60 chars; no emojis unless part of product name; catchy, benefit-focused |
| Gallery | 1270×760 px recommended; readable, show product value |
| Demo video | <2 minutes; optional but recommended |
| First comment | Post immediately; story-driven, not feature list; significantly impacts engagement |
| Topic tags | 3–5 relevant; match Product Hunt taxonomy |
| Practice | Guideline |
|---|---|
| Timing | Tuesday–Thursday; 12:01am Pacific works best |
| Narrative | Create story (problem → solution), not feature list |
test cases passed, vs 15 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.