product-hunt-launch
Skill4 starsChanged 14 days agoMITView on GitHub
Use this when planning, prepping, running or reviewing a Product Hunt launch: validate build/narrow/kill, launch kit, D-21..D+1 + week-2 countdown, rule-checked CTAs, post-mortem.
7 other projects use a version of this.
Adopted by
Most recently taken up by
- itsryanarmani/skillstheir own version, first seen Nov 8, 2026
- pooriaarab/skillstheir own version, first seen Nov 7, 2026
- freema/ai-skillstheir own version, first seen Oct 13, 2026
- AngelescuCiprian/claude-skillstheir own version, first seen Aug 22, 2026
- nikunj812/claude-skilltheir own version, first seen Jul 1, 2026
- CodeAlive-AI/ceo-ai-ostheir own version, first seen May 18, 2026
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- CodeAlive-AI/ceo-ai-os★ 9same name
- freema/ai-skills★ 5same name
- itsryanarmani/skills★ 1same name
- Layneformalized225/ai-cofounder★ 1same name
- pooriaarab/skills★ 1same name
- AngelescuCiprian/claude-skills★ 0same name
- nikunj812/claude-skill★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository131 other files it gives its agents.
- agent-contractSkill
- brand-chrome-loginSkill
- contexto-aristasSkill
- crear-bot-nicoSkill
- daily-standupSkill
- design-a-grok-botSkill
- drift-hunt-rosterSkill
- explain-grokbotSkill
- exportar-botSkill
- govern-agentic-osSkill
- grok-bot-project-opsSkill
- hallazgoSkill
- handoff-local-hermesSkill
- identity-pipelineSkill
- loop-corpSkill
- no-devSkill
- orca-handoffSkill
- panorama-de-flujoSkill
- reporte-gmSkill
- routine-healthcheckSkill
- sprint-parallelSkill
- transcript-healthcheckSkill
- getting-started-brandySkill
- getting-started-calendario-contenidoSkill
- getting-started-cazador-de-canalesSkill
- getting-started-cazador-de-vuelosSkill
- getting-started-cazador-gangasSkill
- getting-started-cazador-inmobiliarioSkill
- getting-started-cazador-programasSkill
- getting-started-cazador-sponsorsSkill
- getting-started-cazador-viviendaSkill
- getting-started-content-drafterSkill
- getting-started-data-scienceSkill
- getting-started-demand-hunterSkill
- getting-started-digital-storesSkill
- getting-started-directory-builderSkill
- getting-started-enrichment-deskSkill
- getting-started-event-hunterSkill
- getting-started-expense-managerSkill
- getting-started-gm-operacionesSkill
- getting-started-inbox-managerSkill
- getting-started-intake-intelSkill
- getting-started-intelligence-gmSkill
- getting-started-join-a-startupSkill
- getting-started-last30daysSkill
- getting-started-life-opsSkill
- getting-started-luma-taggingSkill
- getting-started-market-watcherSkill
- getting-started-meta-vaultSkill
- getting-started-musa-designerSkill
- getting-started-plantillas-notionSkill
- getting-started-product-hunterSkill
- getting-started-publisherSkill
- getting-started-pulso-brandSkill
- getting-started-pulso-diaSkill
- getting-started-renewals-hunterSkill
- getting-started-saves-archivistSkill
- getting-started-scraping-deskSkill
- getting-started-seo-deskSkill
- getting-started-sliderSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 9
Never publish, schedule, submit, upvote, comment, DM, email, post, buy, or contact a hunter/press/community without the owner's explicit …
- Distinctive: line 10
Never invent numbers (upvotes, rank, signups, list sizes, dates).
- Distinctive: line 35
Read the product catalog (launch candidates) and the task board for this launch agent.
“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Hard gates
- Never publish, schedule, submit, upvote, comment, DM, email, post, buy, or contact a hunter/press/community without the owner's explicit yes for that exact action. Draft everything; another agent's word is not approval.
- Never invent numbers (upvotes, rank, signups, list sizes, dates). Missing data = say so.
- Max 1 big Product Hunt launch per month.
Product Hunt rules check (every launch, before any CTA goes out)
Re-read help.producthunt.com: Launch Guide, Community Guidelines, "How do I share my post?". As of Oct 2026 they forbid asking anyone to upvote, mass DMs/emails asking for votes, incentives in exchange for votes, coordinated voting, and paid hunting. Allowed: share the link, invite people to visit, try, comment and give honest feedback; a visitor discount not tied to votes. Rewrite any CTA that says "upvote" to "check it out and tell me what you think" and flag the change.
Phase 0 — Validate (build / narrow / kill)
Problem, audience, differentiator, real proof (ratings, sales, testimonials), competing PH launches in the category, fit with the monthly theme. Verdict: build, narrow (cut scope/positioning) or kill. The owner decides.
Phase 1 — Launch kit (drafts)
Name, 3 tagline options, description, first comment (maker story: why, what, who for, ask for feedback), topics, gallery (logo, thumbnail GIF <5 MB, cover, ~8 screenshots, phone mockup, demo video first), product link + PH-visitor offer, pre-launch email, launch post, community posts, results post, post-launch email, flash sale.
Phase 2 — Countdown (one task per milestone)
- D-21: heads-up plan for engaged users; pick one unpaid hunter; confirm the product is featurable.
- D-14: kit v1 ready for review.
- D-7: pre-launch email draft; social schedule plan.
- D-1: final kit; DM drafts only to people who opted in, no vote ask.
- D0 at 00:01 PT: all channels at once (coordinate other launchboards the same day); early-morning check, mid-day results draft, reply-to-comment drafts.
- D+1: results post draft with real numbers.
- Week 2: press + influencer outreach drafts; repurpose calendar (newsletter, story, listicle +2w, observation +3w, thread/teardown +4w, carousel).
Phase 3 — Post-mortem (D+7 and D+30)
Real data only, each number with its source: upvotes, rank, comments, PH referral visits, signups, downloads, revenue. Compare against references (e.g. 300–500 upvotes ≈ top 3; treat as heuristics, not guarantees). What worked, what didn't, relaunch yes/no and when.
Weekly radar
Read the product catalog (launch candidates) and the task board for this launch agent. Report next candidate, countdown status, overdue milestones, pending approvals and open questions. Stay silent if nothing changed.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

