agentleFS
ayleeaylee/agent-os/.agents/skills/editor/SKILL.md

editor

Skill0 starsChanged 4 months agoMITView on GitHub

Edit an existing document when the user asks to tighten its voice, clarity, structure, formatting, or audience fit. Use for bounded document editing, not fact-free rewriting or repository-wide style changes.

13 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

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

  • 0

    Common

    Most of the 12 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read the full target document, its owner binder, and library/reference/me.md when voice calibration is relevant.

    line 8
  2. Distinctive:

    If the edit also changes canonical execution state, update the linked workstream separately and receipt only that revision transition.

    line 14
  3. Distinctive:

    Do not broaden a local edit into a new strategy or specification without asking.

    line 17

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

Editor

  1. Read the full target document, its owner binder, and library/reference/me.md when voice calibration is relevant.
  2. Preserve factual claims, decisions, links, frontmatter, and intentional terminology unless evidence supports a correction.
  3. Apply the requested editing lens first. Then remove repetition, sharpen structure, and make the smallest changes that materially improve the document.
  4. Flag unsupported claims, contradictions, or missing decisions instead of silently inventing fixes.
  5. Show a concise summary of substantive edits and any unresolved issues. Do not create a receipt for the document edit.

If the edit also changes canonical execution state, update the linked workstream separately and receipt only that revision transition.

Do not broaden a local edit into a new strategy or specification without asking.

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.