launch-community-drafts
Skill0 starsChanged 16 days agoMITView on GitHub
Trigger: Show HN, r/macapps post, Product Hunt launch, launch post, X thread, LinkedIn post. Draft community and social launch texts, checked against each channel's rules.
In this repository5 other files it gives its agents.
- launch-cross-postSkill
- launch-directoriesSkill
- launch-kitSkill
- launch-listsSkill
- launch-trackerSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 5 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Use when the user wants launch texts for communities (Reddit, Hacker News, Product Hunt, Indie Hackers) or social networks (LinkedIn, X, …
- Very specific: line 18
Check each channel's gate before drafting (references/channels.md): account karma or age, cooldowns, main feed versus megathread.
- Very specific: line 19
Run scripts/check-draft.py <draft> --channel <channel> on every draft and fix what it reports.
- Distinctive: line 20
Never post, submit or schedule.
- Distinctive: line 21
Never ask for votes.
- Distinctive: line 35
Read the kit and any existing posts by the maker for voice.
- Distinctive: line 36
Check the gate for each requested channel.
- Very specific: line 38
Run the checker; fix and re-run until it prints ok.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
Activation Contract
Use when the user wants launch texts for communities (Reddit, Hacker News, Product Hunt, Indie Hackers) or social networks (LinkedIn, X, Threads).
Hard Rules
- These are drafts for the maker to rewrite in their own voice. Several communities ban AI-written posts (r/opensource) or auto-remove them (r/macapps); say so with every draft.
- Facts come from
docs/launch/<slug>/kit.mdand the maker's own texts; quote their phrasing where it exists. Never invent anecdotes, numbers or competitor facts. - Check each channel's gate before drafting (
references/channels.md): account karma or age, cooldowns, main feed versus megathread. If the gate is closed, say when it opens and draft for the allowed place. - Run
scripts/check-draft.py <draft> --channel <channel>on every draft and fix what it reports. - Never post, submit or schedule. The maker does, or the user says yes explicitly for that one action.
- Never ask for votes.
Decision Gates
| Channel | Template | Check |
| r/macapps (main feed or megathread) | assets/reddit-pcp.md | reddit-pcp |
| Show HN | assets/show-hn.md | show-hn |
| Product Hunt | assets/product-hunt.md | product-hunt |
| LinkedIn, X, Threads | assets/social.md, one file per network (linkedin.md, x.md, threads.md): the checker reads the whole file | linkedin, x, threads |
| r/opensource | No draft: the maker writes it; offer a rules check only | reddit |
Execution Steps
- Read the kit and any existing posts by the maker for voice.
- Check the gate for each requested channel; re-read the live rules page when one is cited.
- Fill the template into
docs/launch/<slug>/drafts/<channel>.md. - Run the checker; fix and re-run until it prints
ok. - Present each draft with its gate status and what the maker should personalize.
Output Contract
Return per channel: draft path, checker result, gate status (open, megathread, blocked until a date), and the personalization notes.
References
../../references/channels.md: gates, formats and rules per channel.scripts/check-draft.py --help: mechanical checks (length, em dashes, PCP parts, direct downloads, Show HN title, vote requests).
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.

