product-hunt-launch▌
kostja94/marketing-skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
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.
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:
- Product type: SaaS, AI tool, app, Chrome extension
- Launch readiness: Landing page, screenshots, tagline, first comment
- 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
How to use product-hunt-launch on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add product-hunt-launch
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches product-hunt-launch from GitHub repository kostja94/marketing-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate product-hunt-launch. Access the skill through slash commands (e.g., /product-hunt-launch) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.8★★★★★72 reviews- ★★★★★Nikhil Gill· Dec 28, 2024
product-hunt-launch fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Shikha Mishra· Dec 24, 2024
Registry listing for product-hunt-launch matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Valentina Jackson· Dec 4, 2024
product-hunt-launch has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Valentina White· Dec 4, 2024
product-hunt-launch is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Yuki Bansal· Nov 23, 2024
Solid pick for teams standardizing on skills: product-hunt-launch is focused, and the summary matches what you get after install.
- ★★★★★Hassan Perez· Nov 19, 2024
We added product-hunt-launch from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Yash Thakker· Nov 15, 2024
product-hunt-launch reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Mei Sharma· Oct 14, 2024
We added product-hunt-launch from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Liam Garcia· Oct 10, 2024
Solid pick for teams standardizing on skills: product-hunt-launch is focused, and the summary matches what you get after install.
- ★★★★★Dhruvi Jain· Oct 6, 2024
I recommend product-hunt-launch for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
showing 1-10 of 72