post-producthunt
Skill9 starsChanged 2 months agoMITView on GitHub
Adapt and publish campaign items on Product Hunt — launch kits (tagline, description, maker comment) prepared for manual launch
In this repository29 other files it gives its agents.
- content-writingSkill
- image-generationSkill
- post-blueskySkill
- post-devtoSkill
- post-facebookSkill
- post-hackernewsSkill
- post-indiehackersSkill
- post-linkedinSkill
- post-mediumSkill
- post-producthuntSkill
- post-redditSkill
- post-substackSkill
- post-threadsSkill
- post-xSkill
- social-campaignSkill
- content-writingSkill
- image-generationSkill
- post-blueskySkill
- post-devtoSkill
- post-facebookSkill
- post-hackernewsSkill
- post-indiehackersSkill
- post-linkedinSkill
- post-mediumSkill
- post-redditSkill
- post-substackSkill
- post-threadsSkill
- post-xSkill
- social-campaignSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 42
Never solicit votes off-platform.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Product Hunt Adapter
Facts live in platforms/producthunt.json (60-char tagline, launch asset
requirements). PH historically sits behind Cloudflare bot detection —
manual launch is the supported path, and a complete launch kit makes it easy.
What PH rewards (culture)
- "What it does, for whom" taglines — concrete beats clever.
- A demo GIF/screenshots that show the product working.
- A maker comment with the real story: why you built it.
- Launch-day presence: the maker answers every comment personally.
Drafting from the content graph (launch kit)
- name (≤40), tagline (≤60) from
core-claim— "{does what} for {whom}". context→ problem paragraph of the description.proof→ key-features list.demo/link→ product URL + gallery assets (media manifest).roadmap→ "what's next" line in the description.cta→ maker comment: personal, invitational, first-person.- Disclosures: maker comments ARE the disclosure — "I built this".
Publishing
manualonly (launch submission is web-only). The draft package contains the full kit: name, tagline, description, maker comment, media manifest, topic suggestions.- PH API v2 is read-oriented — no launch endpoint; not implemented.
- Launch timing is a human decision (Tue–Thu convention is folklore, the data file says so).
Genuine engagement
- The maker answers comments all launch day — that conversation is the point.
- Never solicit votes off-platform; PH explicitly prohibits vote-rings.
Pitfalls
- One launch per product; re-launches need a substantial update.
- Missing gallery/demo assets sinks a launch — check the media manifest.
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.

