draft
Skill6 starsChanged 3 days agoMITView on GitHub
Draft a post for a specific venue — combines positioning from data/product.md, the venue's posting rules, and a marketing skill pack's technique when the user has one installed, then files the draft into the pipeline with full frontmatter. Also searches the web for threads worth answering, prepares talking points for a reply in someone else's thread and files the thread, lead and reply records. Use when the user says "draft a post for <venue>", "write the Product Hunt launch", "find threads worth answering", "help me reply to this thread", or similar.
25 other projects use a version of this.
Adopted by
Most recently taken up by
- shoot16625/note-clitheir own version, first seen Nov 15, 2026
- Nbill27/academic-writing-skillstheir own version, first seen Nov 15, 2026
- PeterPartridge/CooperativeAICodingtheir own version, first seen Nov 8, 2026
- yuryalencar/ai-skillstheir own version, first seen Nov 1, 2026
- jigripokri/POHAtheir own version, first seen Nov 1, 2026
- danicat/speedgraphertheir own version, first seen Oct 17, 2026
Used with
Projects with it also use outline, onboard and 2 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
VortiagoSkilloutline
Conventions and efficient workflows for Outline knowledge bases via mcp-outline tools. Use when creating, editing, restructuring, or diagramming Outline documents — covers Outline markdown quirks (mermaidjs code fences), document and collection structure, string-match editing, staged rewrites, batch operations, and search status filters.
Also in 3 projects that use this
SentrySkillonboard
Onboard a service to sentry-options. Use when integrating a new service, creating schemas, or setting up the multi-repo sentry-options workflow.
Also in 3 projects that use this
AnthropicSkillstatus
Case status summary by audience — client-facing (plain language), internal (for the professor), or court-ready (formal caption format per local rules). Same facts, different framing and depth. Use when a student needs to update the client, brief the professor, or prepare a court status report.
Also in 3 projects that use this
SentrySkillreview
Fixture review skill.
Also in 5 projects that use this
Other versions25 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 25
- anthropics/claude-for-legal★ 9.5ksame name
- jigripokri/POHA★ 121same name
- tance-mang/chinese-webnovel-skills★ 97same name
- danicat/speedgrapher★ 52same name
- alirezarezvani/gaios★ 50same name
- richard-kim-79/archora-skills★ 49same name
- drafthq/draft★ 40same name
- coolxeo/grok-bot-skills★ 8same name
- vercel-labs/workflow-campaign-demos★ 6same name
- imankulov/skills★ 4same name
15 more not listed
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.
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 2 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 23 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 21
If the venue's rules are marked unverified, tell the user to check them before publishing.
- Distinctive: line 29
Technique: If the user has a marketing skill pack installed and it has a matching skill (copywriting, launch strategy, the venue's …
- Very specific: line 35
File it: Write data/drafts/<platform>/YYYY-MM-DD-<slug>.md (<platform> is the schema's platform value.
- Very specific: line 56
Link the graph: Add a link to the draft under the venue file's ## Posts heading (create the heading if it doesn't exist yet), and an …
- Very specific: line 73
Never fabricate proof — pull claims only from data/product.md's Proof section or a selling point whose evidence is not hypothesis.
- Very specific: line 81
Find: When asked to find threads, search the venues in data/communities.md the user named for the problem phrases in data/product.md …
“Common” is measured: kept by at least 6 in 10 of the 23 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
Draft a post
A draft is only useful if it fits the venue's rules, carries the product's positioning, and states why it exists. This skill produces the draft and the record.
Steps
- Preconditions.
data/product.mdmust be filled: What is it, Ideal customer profile, Positioning and Messaging pillars have content. If one of them still shows a bare ✏️, run the setup skill first. A section marked✏️ skipped <date>does not block a draft: say what is missing, and ask for the one fact the draft needs if it needs one. Identify the target venue entity (data/community-<slug>.md, ordata/communities/reddit/<name>.mdfor subreddits); read itsnotes(posting rules, flair, timing) andplatform. If the venue's rules are marked unverified, tell the user to check them before publishing. - Intent. Establish with the user (or propose):
goal(awareness | conversion | positioning | credibility | retention),success(one observable signal), and which messagingpillarthis post carries. A post whose goal you can't name isn't worth drafting. Pick the argument fromdata/selling-points/(stage: validatedorpromoted) before inventing one, and checkdata/audiences/for what to avoid with this crowd. - Technique. If the user has a marketing skill pack installed and it has a matching skill (copywriting, launch strategy, the venue's channel), apply it for the copy. Baseline rules regardless: open with what the reader can do or learn — never the origin story; match the venue's native tone; on community venues, write as a member sharing work, not a marketer placing content.
File it. Write
data/drafts/<platform>/YYYY-MM-DD-<slug>.md(<platform>is the schema'splatformvalue; for Reddit the folder nests per subreddit,data/drafts/reddit/<subreddit>/— the rule is inAGENTS.md, What goes where):--- type: post pillar: <slug or null> goal: <goal> success: "<one line>" stage: draft platform: <platform> created: <today> published: null --- # <Post title> <post body, ready to copy-paste to the venue>- Link the graph. Add a link to the draft under the venue file's
## Postsheading (create the heading if it doesn't exist yet), and an inclusion link from the pillar's hub (data/pillars/<pillar>.md) so the post stays reachable in the tree. - Validate.
iwe schema validatemust pass. In a git repository, commitdraft: <venue> — <title>. - On publish (when the user reports it's live): set
resource,published,stage: published, clearstatus, and move the doc to the same path underdata/posts/:iwe rename data/drafts/<platform>/<file> data/posts/<platform>/<file>.
Rules
- One venue per draft — venues have different rules; a cross-posted text is a smell.
- Titles do most of the work; offer the user 2–3 title options before finalizing.
- Never fabricate proof — pull claims only from
data/product.md's Proof section or a selling point whoseevidenceis nothypothesis.
Replying in someone else's thread
The user writes the words of every comment posted in other people's threads; this mode prepares and records, it never posts.
- Find. When asked to find threads, search the venues in
data/communities.mdthe user named for the problem phrases indata/product.md(Customer language) and the watchlist indata/mentions.md, not the product name. Skip threads already filed (iwe find --filter '{type: thread}' --project '$title,resource'). Present a shortlist: link, age, what was asked, and why it fits. - Read. For the thread the user picks, read the whole thread and the
venue's
notes. Say whether the venue allows naming the product here. - Talking points. Give two to four talking points that answer what was literally asked, the facts to get right, and anything to avoid. No finished comment unless the user asks for one; if they do, mark it as a draft for them to rewrite.
- File once the user says it is posted, in this order — this is the one
place the order is written, and every other document points here: the
thread page
data/threads/<platform>-<slug>.md(link the venue in its body); a leaddata/leads/<handle-slug>.md(stage: new,fit,## Where we found them,## What they need) if the person answered may want the product and has no lead or person record yet; then the replydata/replies/YYYY-MM-DD-<platform>-<slug>.mdwith## ContextopeningPerson: [<handle>](<lead or person>),## Our replyquoting the comment exactly as posted,names_product, andorigin(humanwhen the user wrote it,agent-editedoragentonly when they say so). Inclusion-link the reply under the thread page's## Repliesand fromdata/replies.md; link the lead fromdata/leads.md. - Review. Three days after
published, setoutcomeandreviewed(the update skill proposes it); raise the outcome whenever the conversation moves. - Validate.
iwe schema validate. In a git repository, commitreply: <venue> — <thread title>.
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.

