agentleFS
holt-osholt-os/holt/skills/rewrite/SKILL.md

rewrite

Skill7 starsChanged 26 days agoMITView on GitHub

Tighten and clarify a piece of text without changing its meaning. Use for a neutral clarity pass on text the user provides.

8 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 4

    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:

    Prefer plain words over inflated ones ("use" not "utilize", "help" not "facilitate").

    line 17
  2. Distinctive:

    Keep the author's voice and register.

    line 19
  3. Distinctive:

    Before: I just wanted to reach out in order to see if you might possibly have some availability to maybe hop on a quick call sometime.

    line 24
  4. Distinctive:

    After: Do you have time for a quick call this week?

    line 26

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

rewrite

When to use

The user pastes a paragraph, email, or passage and wants it cleaner and clearer while keeping the same meaning. This is a neutral clarity pass, distinct from a voice-anchored writing task: keep the author's own voice unless a tone is requested.

Instructions

  1. Preserve intent and every fact. Do not add claims, drop caveats, or change the point being made.
  2. Cut filler and hedging: "just", "really", "I think that", "in order to", throat-clearing intros, and redundant phrases.
  3. Prefer plain words over inflated ones ("use" not "utilize", "help" not "facilitate").
  4. Vary sentence length so it reads naturally; break up run-ons, and do not make everything staccato.
  5. Keep the author's voice and register. Only shift tone (more formal, warmer, punchier) if the user asks for it.
  6. Return only the rewritten text, then one short line noting what you changed (for example: "tightened, cut hedging, split two long sentences").

Example

Before: I just wanted to reach out in order to see if you might possibly have some availability to maybe hop on a quick call sometime.

After: Do you have time for a quick call this week?

Changed: cut hedging and filler, made it a direct ask.

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.