skills/channels/community/product-hunt-launch/SKILL.md
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.
npx skillsauth add kostja94/marketing-skills product-hunt-launchInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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.
Read project context first: If .claude/project-context.md or .cursor/project-context.md exists, use Sections 1–4, 5, 6, 8, 9 for submission content.
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 | | Engagement | Reply to every comment; thank supporters; answer questions | | Avoid | Begging for upvotes (risk of shadowban) |
Principle: Product Hunt is a visibility amplifier and credibility boost—not primarily a customer acquisition channel.
| Outcome | Upvotes | Placement | |---------|---------|-----------| | Poor | 50–100 | — | | Average | 200–400 | Top 10 | | Good | 500–800 | Top 5 | | Great | 800+ | Product of the Day |
| Offering | Use When | |----------|----------| | Product Hunt Daily | Newsletter feature; high-intent audience | | Social promotion | PH shares on X, LinkedIn; launch-day amplification | | Featured placement | Paid promotion options |
data-ai
When the user wants to add or optimize Twitter Card metadata for X (Twitter) link previews. Also use when the user mentions "Twitter Card," "twitter:card," "twitter:image," "twitter:title," "X preview," or "tweet preview." For Facebook/LinkedIn previews, use open-graph.
testing
When the user wants to add or optimize Open Graph metadata for social sharing. Also use when the user mentions "Open Graph," "og:tags," "og:title," "og:image," "og:description," "Facebook preview," "LinkedIn preview," or "social share preview." For X (Twitter) link previews, use twitter-cards. For SERP title/description, use title-tag and meta-description.
tools
When the user wants to create, optimize, or structure Terms of Service page. Also use when the user mentions "terms of service," "terms and conditions," "terms of use," "user agreement," "ToS," "legal terms," "service agreement," or "terms page." For legal overview page, use legal-page-generator.
development
When the user wants to create or optimize a shipping or delivery information page. Also use when the user mentions "shipping," "delivery," "shipping policy," "delivery times," "shipping page," "free shipping," "shipping rates," "delivery options," "shipping info," "cross-border shipping," "international delivery," or "order tracking." For legal overview, use legal-page-generator.