/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,"
$ npx -y skills add kostja94/marketing-skills --skill product-hunt-launch --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/product-hunt-launch
Context preview
The summary Claude sees to decide when to auto-load this skill.
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,"
SKILL.md
product-hunt-launch.SKILL.mdname: product-hunt-launch
description: 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.
metadata:
version: 1.1.0
Channels: Product Hunt Launch
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.
Initial Assessment
**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: 1. **Product type**: SaaS, AI tool, app, Chrome extension 2. **Launch readiness**: Landing page, screenshots, tagline, first comment 3. **Hunter**: Self-hunt or Top Hunter (optional but helps)
30-Day Preparation Plan
| 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 |
Product Hunt Fields
| 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 |
Launch Day Strategy
| 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.
Realistic Expectations
| Outcome | Upvotes | Placement | |---------|---------|-----------| | Poor | 50–100 | — | | Average | 200–400 | Top 10 | | Good | 500–800 | Top 5 | | Great | 800+ | Product of the Day |
Beyond Listing
| 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 |
Post-Launch
- Continue engaging with new users
- Thank-you emails to supporters
- Ask for feedback
- See **directory-submission** for other directories; **cold-start-strategy** for full launch plan
Output Format
- **Readiness checklist** (tagline, gallery, first comment, topic tags)
- **First comment** draft (story-driven)
- **Tagline** options (≤60 chars)
- **30-day timeline** (if planning ahead)
Related Skills
- **directory-submission**: Taaft, G2, curated lists; Product Hunt is one directory—see for multi-platform submission
- **cold-start-strategy**: Full launch plan; Product Hunt as channel
- **indie-hacker-strategy**: Indie hacker Product Hunt, first 100 users
- **media-kit-page-generator**: Press kit, screenshots for launch
- **analytics-tracking**: UTM for Product Hunt traffic attribution
Read more
name: product-hunt-launch description: 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. metadata: version: 1.1.0
Channels: Product Hunt Launch
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.
Initial Assessment
**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: 1. **Product type**: SaaS, AI tool, app, Chrome extension 2. **Launch readiness**: Landing page, screenshots, tagline, first comment 3. **Hunter**: Self-hunt or Top Hunter (optional but helps)
30-Day Preparation Plan
| 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 |
Product Hunt Fields
| 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 |
Launch Day Strategy
| 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.
Realistic Expectations
| Outcome | Upvotes | Placement | |---------|---------|-----------| | Poor | 50–100 | — | | Average | 200–400 | Top 10 | | Good | 500–800 | Top 5 | | Great | 800+ | Product of the Day |
Beyond Listing
| 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 |
Post-Launch
- Continue engaging with new users
- Thank-you emails to supporters
- Ask for feedback
- See **directory-submission** for other directories; **cold-start-strategy** for full launch plan
Output Format
- **Readiness checklist** (tagline, gallery, first comment, topic tags)
- **First comment** draft (story-driven)
- **Tagline** options (≤60 chars)
- **30-day timeline** (if planning ahead)
Related Skills
- **directory-submission**: Taaft, G2, curated lists; Product Hunt is one directory—see for multi-platform submission
- **cold-start-strategy**: Full launch plan; Product Hunt as channel
- **indie-hacker-strategy**: Indie hacker Product Hunt, first 100 users
- **media-kit-page-generator**: Press kit, screenshots for launch
- **analytics-tracking**: UTM for Product Hunt traffic attribution
Markdown skill library for AI agents - SEO, content, pages, paid ads, channels, strategies. Add project context + skills; your agent delivers tailored, production-ready output. Works with Cursor, Claude Code, OpenClaw, Lovable, and any AI that reads markdown.
Repo: kostja94/marketing-skills
Other skills on kostja94-marketing-skills.
- /google-search-console
When the user wants to analyze Google Search Console data, use the GSC API, or interpret search performance. Also use when the user mentions "GSC," "Search Console," "indexing report," "Core Web Vitals," "Enhancements," "Insights report," "search performance," "search queries,"
Open skill - /seo-monitoring
When the user wants to build an SEO data analysis system, monitor indexing/traffic/keywords/backlinks, or set up benchmarks. Also use when the user mentions "SEO data analysis," "SEO monitoring," "article database," "traffic benchmark," "penalty recovery," "SEO work document,"
Open skill - /ai-traffic
When the user wants to track AI search traffic in GA4 or GSC. Also use when the user mentions "AI traffic," "ChatGPT referral," "Perplexity traffic," "AI Overviews," "GA4 AI sources," "AI search analytics," "track AI referrals," "AI search traffic," "Claude traffic," or "how to
Open skill - /traffic
When the user wants to analyze website traffic sources, attribution, or dark traffic. Also use when the user mentions "traffic sources," "dark traffic," "direct traffic," "UTM parameters," "traffic attribution," "channel attribution," "attribution optimization," "channel
Open skill - /tracking
When the user wants to set up, audit, or optimize analytics tracking (GA4, events, conversions). Also use when the user mentions "Google Analytics," "GA4," "event tracking," "conversions," "attribution model," "gtag," "data layer," "GA4 setup," "conversion tracking," "event
Open skill - /community-forum
When the user wants to promote via forums, communities, or invite users to join a community. Also use when the user mentions "forum promotion," "Indie Hacker," "Hacker News," "community growth," "Discord promotion," "vertical community," "brand encyclopedia," "Wikipedia,"
Open skill