agentleFS
Sign inStart free
coolxeocoolxeo/grok-bot-skills/skills/writing/draft/SKILL.md

draft

Skill7 starsChanged 16 days agoMITView on GitHub

Use this when writing or expanding an article section by section. Never generate a full article in one shot.

24 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use onboard, status 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.
  • 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

  • VercelSkill

    setup

    Set up Vercel CLI and project configuration. Use when the user says "set up Vercel", "configure Vercel", "link to Vercel", or "vercel init".

    Also in 4 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

7 rules. 0 are common, 7 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 22 edited versions we read keep these.

  • 7

    Distinctive

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

    Write one section at a time from a signed outline and interview notes.

    line 11
  2. Distinctive:

    No em dashes. Periods, commas, parentheses.

    line 21
  3. Distinctive:

    No formula phrases: not just X but Y, in today's world, it's important to note, a key takeaway is, let's explore.

    line 24
  4. Distinctive:

    Every paragraph must add a new fact or move.

    line 25
  5. Distinctive:

    Never invent numbers, quotes, or sources.

    line 30
  6. Distinctive:

    After each section, reread from the top for tone shift and repeated points.

    line 36
  7. Distinctive:

    If the section fights the outline, say so and go back to Outline.

    line 37

“Common” is measured: kept by at least 6 in 10 of the 22 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

Write one section at a time from a signed outline and interview notes. Sculpt, do not dump.

Before prose

  1. Restate the thesis in one sentence. If it is vague or trying to say too many things, fix the thesis first.
  2. Name 2 voice patterns you will keep (short punchline paragraph, concrete number, first person, etc.).
  3. Say which section you are writing and why that one is next.

Guard rails

  • No em dashes. Periods, commas, parentheses.
  • Vary sentence length. Do not stack three similar sentences.
  • Banned: leverage, comprehensive, pivotal, delve, showcase, intricate, landscape, tapestry, transformative, paradigm, robust, seamless, unlock, dynamic.
  • No formula phrases: not just X but Y, in today's world, it's important to note, a key takeaway is, let's explore.
  • Every paragraph must add a new fact or move. Restating in new words is a cut.
  • Open with a claim, scene, or problem. Not "Have you ever…"
  • End concrete. No motivational poster.
  • Prose over bullets unless the reader is scanning steps.
  • Contrastive "not X, but Y" at most twice in a long piece. Prefer the positive claim.
  • Never invent numbers, quotes, or sources. Flag a gap instead.

How

  • One section, then stop for sign-off unless the writer asked for more.
  • Offer 2 options when the line is load-bearing (hook, invoice, takeaway).
  • After each section, reread from the top for tone shift and repeated points.
  • If the section fights the outline, say so and go back to Outline. Do not polish a broken arc.

Source: adapted from Nadiem Mahmoud, draft. MIT; see third-party notices.

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.

Check your setup, free