agentleFS
iwe-orgiwe-org/marketing-workspace/.claude/skills/draft/SKILL.md

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

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.
  • VortiagoSkill

    outline

    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

  • SentrySkill

    onboard

    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

  • AnthropicSkill

    status

    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

  • SentrySkill

    review

    Fixture review skill.

    Also in 5 projects that use this

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
  1. Distinctive:

    If the venue's rules are marked unverified, tell the user to check them before publishing.

    line 21
  2. Distinctive:

    Technique: If the user has a marketing skill pack installed and it has a matching skill (copywriting, launch strategy, the venue's …

    line 29
  3. Very specific:

    File it: Write data/drafts/<platform>/YYYY-MM-DD-<slug>.md (<platform> is the schema's platform value.

    line 35
  4. Very specific:

    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 …

    line 56
  5. Very specific:

    Never fabricate proof — pull claims only from data/product.md's Proof section or a selling point whose evidence is not hypothesis.

    line 73
  6. Very specific:

    Find: When asked to find threads, search the venues in data/communities.md the user named for the problem phrases in data/product.md …

    line 81

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

  1. Preconditions. data/product.md must 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, or data/communities/reddit/<name>.md for subreddits); read its notes (posting rules, flair, timing) and platform. If the venue's rules are marked unverified, tell the user to check them before publishing.
  2. Intent. Establish with the user (or propose): goal (awareness | conversion | positioning | credibility | retention), success (one observable signal), and which messaging pillar this post carries. A post whose goal you can't name isn't worth drafting. Pick the argument from data/selling-points/ (stage: validated or promoted) before inventing one, and check data/audiences/ for what to avoid with this crowd.
  3. 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.
  4. File it. Write data/drafts/<platform>/YYYY-MM-DD-<slug>.md (<platform> is the schema's platform value; for Reddit the folder nests per subreddit, data/drafts/reddit/<subreddit>/ — the rule is in AGENTS.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>
  5. 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 inclusion link from the pillar's hub (data/pillars/<pillar>.md) so the post stays reachable in the tree.
  6. Validate. iwe schema validate must pass. In a git repository, commit draft: <venue> — <title>.
  7. On publish (when the user reports it's live): set resource, published, stage: published, clear status, and move the doc to the same path under data/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 whose evidence is not hypothesis.

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.

  1. Find. When asked to find threads, search the venues in data/communities.md the user named for the problem phrases in data/product.md (Customer language) and the watchlist in data/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.
  2. 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.
  3. 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.
  4. 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 lead data/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 reply data/replies/YYYY-MM-DD-<platform>-<slug>.md with ## Context opening Person: [<handle>](<lead or person>), ## Our reply quoting the comment exactly as posted, names_product, and origin (human when the user wrote it, agent-edited or agent only when they say so). Inclusion-link the reply under the thread page's ## Replies and from data/replies.md; link the lead from data/leads.md.
  5. Review. Three days after published, set outcome and reviewed (the update skill proposes it); raise the outcome whenever the conversation moves.
  6. Validate. iwe schema validate. In a git repository, commit reply: <venue> — <thread title>.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.