New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Product Hunt Launch Plan

by ognjengt in ognjengt/founder-skills

Creates a comprehensive, personalized Product Hunt launch plan to rank

MITAuto-check passedMarketing & SEO

Install Product Hunt Launch Plan

skills CLI
$ npx skills add ognjengt/founder-skills --skill product-hunt-launch-plan -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install ognjengt/founder-skills product-hunt-launch-plan --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/ognjengt/founder-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/product-hunt-launch-plan .claude/skills/product-hunt-launch-plan && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
product-hunt-launch-plan
GitHub stars
447
Token cost
~2.5k tokens
SKILL.md length
1,095 words
Files
2 (incl. references)
Skills in repo
15
Repo updated
First seen
Licence
MIT

At a glance

Creates a comprehensive, personalized Product Hunt launch plan to rank

  • Works in 6 steps: MANDATORY: Read Reference Files FIRST → Check for Business Context → Discovery Questions (MANDATORY) → …
  • Tasks that involve Product launch strategy
  • SKILL.md covers Purpose, Execution Logic, Task Execution and Writing Rules, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Product Hunt Launch Plan is an agent skill from ognjengt/founder-skills. Creates a comprehensive, personalized Product Hunt launch plan to rank

Its SKILL.md is about 2.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/ultimate_product_hunt_launch_guide.md`).

It sits in Marketing & SEO, covering Product launch strategy. The repository describes itself as: Claude skills for founders. The licence is MIT.

When your agent uses it

  • Tasks that involve Product launch strategy

Example prompts

  • “Use the product-hunt-launch-plan skill to create a comprehensive, personalized Product Hunt launch plan to rank”
  • “/product-hunt-launch-plan”

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. MANDATORY: Read Reference Files FIRST
  2. Check for Business Context
  3. Discovery Questions (MANDATORY)
  4. Analyze & Personalize
  5. Generate Personalized Launch Plan
  6. Format and Verify

What it can do on your machine

Read from SKILL.md and the folder at commit a45931c. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Product Hunt Launch Plan loads about 2.5k tokens when it runs, and up to ~6k if it reads all its reference files. Until then it costs about 24 tokens; SKILL.md has 1,095 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~24
When it runs · the whole SKILL.md, loaded when a task matches
~2.5k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from ognjengt/founder-skills at commit a45931c, republished under its MIT licence (© ognjengt). 1,095 words, ~2,537 tokens.

Download SKILL.mdSave it as .claude/skills/product-hunt-launch-plan/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
product-hunt-launch-plan
description
Creates a comprehensive, personalized Product Hunt launch plan to rank

Product Hunt Launch Plan

Purpose

Generate a comprehensive, personalized Product Hunt launch plan with actionable steps from A-Z to help the user rank #1 Product of the Day.

Execution Logic

Check $ARGUMENTS first to determine execution mode:

If $ARGUMENTS is empty or not provided:

Respond with: "product-hunt-launch-plan loaded. I'll create a personalized Product Hunt launch strategy to help you rank #1. Let me gather some information about your product first."

Then proceed to the Discovery Questions phase.

If $ARGUMENTS contains content:

Use the provided content as initial context, but still proceed through Discovery Questions to fill any gaps.

Task Execution

When user engages with this skill:

1. MANDATORY: Read Reference Files FIRST

BLOCKING REQUIREMENT — DO NOT SKIP THIS STEP

Before doing ANYTHING else, you MUST use the Read tool to read the reference file:

Read: ./references/ultimate_product_hunt_launch_guide.md

What you will find:

  • Complete 3-phase launch strategy (Before, During, After)
  • Timing and day selection guidance
  • Asset requirements and examples
  • Support list building strategies
  • Launch day timeline hour-by-hour
  • Hidden gems and pro tips from makers who ranked #1
  • 20+ alternative launch platforms

DO NOT PROCEED to Step 2 until you have read this file and have the complete guide in context.

2. Check for Business Context

Check if FOUNDER_CONTEXT.md exists in the project root.

  • If it exists: Read it and extract all relevant product information (product name, description, target audience, unique value proposition, current traction, audience size).
  • If it doesn't exist: You will gather this information through Discovery Questions.
3. Discovery Questions (MANDATORY)

Ask up to 10 targeted questions to personalize the launch plan.

Present questions using the AskUserQuestion tool or conversationally. Gather:

  1. Product Basics

    • What is your product name and one-line description?
    • What problem does it solve and for whom?

  2. Current State

    • What's your current launch date (or target timeframe)?
    • Do you have a Product Hunt account? Is it active/warmed?

  3. Audience & Reach

    • How large is your email list?
    • What's your Twitter/X following size?
    • Are you active in any communities (Indie Hackers, Discord, Slack)?

  4. Assets Readiness

    • Do you have product screenshots/demo video ready?
    • Do you have a landing page live?

  5. Support Network

    • Do you have founder friends who could support the launch?
    • Have you supported other Product Hunt launches before?

  6. Goals & Constraints

    • What's your primary goal? (users, awareness, investors, validation)
    • Any constraints? (budget, time, team size)

Adapt questions based on FOUNDER_CONTEXT.md if available. Skip questions already answered there.

4. Analyze & Personalize

Based on gathered information, assess:

  • Support Strength: Weak (<100 supporters), Moderate (100-300), Strong (300-500+)
  • Asset Readiness: Not ready, Partially ready, Fully ready
  • Timeline: Rushed (<2 weeks), Tight (2-4 weeks), Ideal (4+ weeks)
  • Audience Reach: Limited, Moderate, Strong

Use this assessment to customize recommendations.

5. Generate Personalized Launch Plan

Create a comprehensive plan with:

Section 1: Executive Summary

  • Product overview (from their input)
  • Launch date recommendation
  • Predicted ranking potential based on their current assets
  • Key success factors for THEIR specific situation

Section 2: Pre-Launch Phase (customize timeline based on their date)

  • Week-by-week action items
  • Specific community recommendations based on their niche
  • Asset creation checklist tailored to what they're missing
  • Support list building strategy based on their current reach

Section 3: Launch Week Preparation

  • Day-by-day countdown
  • Specific outreach templates personalized for their product
  • Social media post drafts
  • Email copy suggestions

Section 4: Launch Day Battle Plan

  • Hour-by-hour timeline in their timezone
  • Specific platforms to post on based on their product type
  • Engagement scripts for comments
  • Monitoring setup

Section 5: Post-Launch Strategy

  • Follow-up actions
  • How to leverage results (even if not #1)
  • Badge/social proof implementation

Section 6: Hidden Gems & Pro Tips Include 5-10 advanced tactics from the reference guide, selected based on relevance to their situation.

Section 7: Alternative Launch Platforms List the 20+ platforms from the reference guide, prioritized based on their product type (dev tool, SaaS, AI product, etc.).

6. Format and Verify
  • Structure output according to Output Format section
  • Complete Quality Checklist self-verification before presenting

Writing Rules

Hard constraints. No interpretation.

Show full SKILL.md (443 more words)Show less
Core Rules
  • Be specific and actionable — no vague advice like "build community"
  • Include exact timelines, numbers, and examples
  • Personalize every recommendation to THEIR product
  • Reference their product name throughout the plan
  • Include templates they can copy/paste
  • Prioritize actions by impact
Personalization Rules
  • If small audience (<500): Focus on community building and reciprocity tactics
  • If large audience (5000+): Focus on coordinated launch and momentum strategies
  • If dev tool: Emphasize Hacker News, DevHunt, GitHub community
  • If AI product: Include AI-specific directories
  • If B2B SaaS: Focus on LinkedIn, professional communities
  • If consumer app: Focus on Twitter/X, visual assets
Honesty Rules
  • Be realistic about their chances based on their current situation
  • If timeline is too tight, say so and suggest rescheduling
  • If assets are weak, prioritize fixing that first
  • Don't promise #1 if their support base is too small

Output Format

markdown
# Product Hunt Launch Plan: [Product Name]

## Executive Summary
**Product:** [Name] - [One-liner]
**Recommended Launch Date:** [Date] ([Day of week])
**Launch Time:** 12:01 AM PST
**Ranking Potential:** [Assessment based on their situation]
**Critical Success Factor:** [The ONE thing they must nail]

---

## Phase 1: Pre-Launch ([X] weeks out)

### Week [X]: [Focus Area]
- [ ] Action item 1
- [ ] Action item 2
...

### Week [X-1]: [Focus Area]
...

---

## Phase 2: Launch Week

### Day -7 to -1: Final Preparations
...

### Launch Day: Hour-by-Hour Battle Plan

**[Time in their timezone] - [Action]**
...

---

## Phase 3: Post-Launch

### Day 1-3: Immediate Actions
...

### Week 1: Capitalize on Results
...

---

## Your Personalized Tips

Based on your situation, focus on these advanced tactics:

1. **[Tip Name]:** [Specific advice for their situation]
...

---

## Alternative Launch Platforms (Prioritized for [Product Type])

### Launch This Week (Alongside Product Hunt)
| Platform | Why It Fits You |
|----------|-----------------|
...

### Launch Next Week
...

---

## Ready-to-Use Templates

### Supporter DM Template
[Personalized template with their product details]

### Launch Day Tweet Thread
[Draft thread they can customize]

### Email to Subscribers
[Draft email copy]

---

## Your Launch Checklist

### Assets Needed
- [ ] Item (Status: Ready/Needed)
...

### Support List Target
- [ ] Category: [X] people (Current: [Y])
...

References

This file MUST be read using the Read tool before creating any launch plan (see Step 1):

FilePurpose
./references/ultimate_product_hunt_launch_guide.mdComplete Product Hunt strategy from Tibo (Maker of the Year 2022), including 3-phase launch process, hidden gems, pro tips, and 20+ alternative platforms

Why this matters: This guide contains battle-tested strategies from someone who has ranked #1 multiple times. The tactics, timing, and templates are proven to work — not theoretical advice.

Quality Checklist (Self-Verification)

Before finalizing output, verify ALL of the following:

Pre-Execution Check
  • I read ./references/ultimate_product_hunt_launch_guide.md before creating the plan
  • I checked for and read FOUNDER_CONTEXT.md if it exists
  • I have the complete guide content in context
Discovery Check
  • I asked targeted questions to understand their specific situation
  • I know their product, audience size, timeline, and assets status
  • I adapted my questions based on available context
Personalization Check
  • Every section references THEIR product by name
  • Recommendations match their audience size and reach
  • Timeline is realistic for their launch date
  • Platform recommendations match their product type
  • Templates include their specific product details
Completeness Check
  • All 3 phases covered (Before, During, After)
  • Hour-by-hour launch day timeline included
  • Hidden gems/pro tips section included
  • Alternative platforms listed and prioritized
  • Ready-to-use templates provided
  • Checklist with current status included
Honesty Check
  • Ranking assessment is realistic
  • Weak areas are called out with solutions
  • Timeline concerns are addressed
  • No false promises of guaranteed #1

If ANY check fails → revise before presenting.

Defaults & Assumptions

Use these unless the user overrides:

  • Launch day: Tuesday, Wednesday, or Thursday (higher traffic)
  • Launch time: 12:01 AM PST (Product Hunt reset time)
  • Target ranking: Top 5 (requires ~500 engaged supporters)
  • Preparation time: 4 weeks ideal minimum
  • Primary goal: User acquisition and validation
  • Hunter strategy: Self-hunt (60% of #1 products are self-hunted)
  • Asset format: Static images prioritized over video (higher engagement)

Document any assumptions made in the Executive Summary.

© ognjengt, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in skills/product-hunt-launch-plan of ognjengt/founder-skills.

  • SKILL.md
  • references/ultimate_product_hunt_launch_guide.md

Open the folder on GitHubat commit a45931c

Compare with similar skills

Product Hunt Launch Plan next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Product Hunt Launch Plan compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Product Hunt Launch Plan this skillognjengt/founder-skills447—~2.5kAutomated safety check: PassMIT
Technical Launch Plannerjamesrochabrun/skills2161 repos~3.8kAutomated safety check: PassMIT
Getxapi ConnectLeoYeAI/openclaw-marketing-skills1k1 repos~715Automated safety check: PassCustom licence
ProducthuntReScienceLab/opc-skills1.8k—~467Automated safety check: PassApache-2.0
Micro SaaS Launchernicepkg/auto-company1958 repos~1.3kAutomated safety check: PassNone
Directory Submissionscoreyhaines31/marketingskills54k2 repos~6.7kAutomated safety check: PassMIT

Similar skills

  • Technical Launch Planner

    jamesrochabrun/skills

    Plan and execute technical product launches for developer tools, APIs, and technical products.

    216 GitHub starsUsed in 1 repo~3.8k tokens
    Marketing & SEOAuto-check passed

  • Getxapi Connect

    LeoYeAI/openclaw-marketing-skills

    Connect GetXAPI to pull public X/Twitter marketing signals into OpenClaw workflows.

    1k GitHub starsUsed in 1 repo~715 tokens
    Marketing & SEOAuto-check passed

  • Producthunt

    ReScienceLab/opc-skills

    Search and retrieve content from Product Hunt. An agent skill from ReScienceLab/opc-skills.

    1.8k GitHub stars~467 tokensUpdated yesterday
    Marketing & SEOAuto-check passed

  • Micro SaaS Launcher

    nicepkg/auto-company

    Expert in launching small, focused SaaS products fast - the indie hacker approach to building profitable software.

    195 GitHub starsUsed in 8 repos~1.3k tokens
    Marketing & SEOAuto-check passed

  • Directory Submissions

    coreyhaines31/marketingskills

    When the user wants to submit their product to startup, SaaS, AI, agent, MCP, no-code, or review directories for backlinks, domain rating, and discovery.

    54k GitHub starsUsed in 2 repos~6.7k tokens
    Marketing & SEOAuto-check passed

  • Producthunt

    FoundDream/miniclawd

    Discover trending tech products, apps, and tools from Product Hunt.

    138 GitHub stars~722 tokensUpdated 8 mo ago
    Marketing & SEOAuto-check passed

More from ognjengt/founder-skills

All 15 skills in this repo

  • Brand Copywriter

    ognjengt/founder-skills

    Writes marketing copy using proven copywriting frameworks. An agent skill from ognjengt/founder-skills.

    447 GitHub stars~3.2k tokensUpdated 4 mo ago
    Auto-check passed

  • Cro Optimization

    ognjengt/founder-skills

    Analyzes landing pages and provides detailed CRO (Conversion Rate Optimization) recommendations.

    447 GitHub stars~2.4k tokensUpdated 4 mo ago
    Auto-check passed

  • Lead Magnet Generator

    ognjengt/founder-skills

    Creates viral lead magnet posts that drive comments and DMs.

    447 GitHub stars~3k tokensUpdated 4 mo ago
    Auto-check passed

  • Linkedin Writer

    ognjengt/founder-skills

    Creates viral LinkedIn posts using proven formats, post templates, and voice matching.

    447 GitHub stars~3.4k tokensUpdated 4 mo ago
    Auto-check passed

  • Marketing Ideas

    ognjengt/founder-skills

    Produces the best marketing ideas for your business by analyzing your FOUNDERCONTEXT and matching it against a curated database of 170+ proven marketing strategies.

    447 GitHub stars~3.1k tokensUpdated 4 mo ago
    Auto-check passed

  • Outreach Specialist

    ognjengt/founder-skills

    Crafts high-converting outreach messages and email sequences for cold outreach, LinkedIn DMs, and follow-ups.

    447 GitHub stars~3.2k tokensUpdated 4 mo ago
    Auto-check passed

Categories

Questions about Product Hunt Launch Plan

What does Product Hunt Launch Plan do?

Creates a comprehensive, personalized Product Hunt launch plan to rank. Product Hunt Launch Plan is an agent skill from ognjengt/founder-skills.

When should I use Product Hunt Launch Plan?

Product Hunt Launch Plan fits situations like: tasks that involve Product launch strategy.

How do I install Product Hunt Launch Plan in Claude Code?

Run `npx skills add ognjengt/founder-skills --skill product-hunt-launch-plan -a claude-code`. Or copy the skill folder (skills/product-hunt-launch-plan in ognjengt/founder-skills) into .claude/skills/product-hunt-launch-plan in your project. Claude Code loads it when a task matches its description.

How do I install Product Hunt Launch Plan in Codex?

Run `npx skills add ognjengt/founder-skills --skill product-hunt-launch-plan -a codex`. Or copy the skill folder (skills/product-hunt-launch-plan in ognjengt/founder-skills) into .agents/skills/product-hunt-launch-plan in your project. Codex loads it when a task matches its description.

Can I use Product Hunt Launch Plan in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ognjengt/founder-skills --skill product-hunt-launch-plan -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/product-hunt-launch-plan, .gemini/skills/product-hunt-launch-plan, .github/skills/product-hunt-launch-plan and .opencode/skills/product-hunt-launch-plan in your project.

What does Product Hunt Launch Plan need to run?

SKILL.md names no scripts, command-line tools or credentials: Product Hunt Launch Plan is instructions for the agent only.

Does Product Hunt Launch Plan access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Product Hunt Launch Plan safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Product Hunt Launch Plan use?

Product Hunt Launch Plan is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Product Hunt Launch Plan use?

About 2.5k tokens (SKILL.md is roughly 10k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.4k tokens, read only when the agent opens those files.

What are the alternatives to Product Hunt Launch Plan?

Skills that share tags, products or a category with Product Hunt Launch Plan: Technical Launch Planner (jamesrochabrun/skills, 216 stars), Getxapi Connect (LeoYeAI/openclaw-marketing-skills, 1k stars), Producthunt (ReScienceLab/opc-skills, 1.8k stars) and Micro SaaS Launcher (nicepkg/auto-company, 195 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Product Hunt Launch Plan?

ognjengt (a GitHub user) maintains it in ognjengt/founder-skills, which has 447 GitHub stars. The repository holds 15 skills in this directory. The repository was last updated on May 18, 2026.

Source: ognjengt/founder-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.