agentleFS
coolxeocoolxeo/grok-bot-skills/skills/writing/coach/SKILL.md

coach

Skill7 starsChanged 18 days agoMITView on GitHub

Use this when a draft needs a structural read before line-edit — thesis, arc, and teach test first, style second.

27 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use research, review and 1 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.
  • NVIDIASkill

    research

    Before designing a feature, research how comparable libraries solve the problem, check best practices, known pitfalls, and upstream changes. Use when starting a new feature, investigating an unfamiliar area, or the user asks to research something.

    Also in 4 projects that use this

  • SentrySkill

    review

    Fixture review skill.

    Also in 4 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 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 23 edited versions we read keep these.

  • 3

    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:

    If any answer is NO, stop scoring voice.

    line 21
  2. Distinctive:

    Before/after for those three

    line 41
  3. Distinctive:

    READ-ONLY. Do not edit the draft.

    line 43

“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

Coach

Developmental edit. Structure and argument first. Do not polish a broken piece.

Triage

Answer YES/NO:

  • Thesis clear? State it in one sentence or say why it is unclear.
  • Structure sound? Name the break if the arc fails.
  • Argument complete? Name gaps, missing evidence, unsupported leaps.

If any answer is NO, stop scoring voice. Send the writer back to Outline or Draft.

If triage passes, score 1–5

  1. Opening — concrete moment vs abstract thesis
  2. Structure — one argument that builds and closes
  3. Natural voice — one person, one sitting; flag AI tells
  4. Rigor — claims have evidence
  5. Teach test — one sentence the reader can steal
  6. Accessibility — specialist words explained
  7. Flow — continuous argument vs bolted sections

A 3 is average. A 5 is publishable. Be honest.

Output

Triage, overall /35, one line per axis, then:

  • Section-by-section notes with quotes
  • Top 3 issues (structural before prose)
  • Before/after for those three

READ-ONLY. Do not edit the draft. The writer decides.

Source: adapted from Nadiem Mahmoud, coach. 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.