agentleFS
redicherediche/skills/clear-writing/SKILL.md

clear-writing

Skill3 starsChanged 39 days agoMITView on GitHub

Writes and revises technical documentation using practical ASD-STE100 principles for clear language. Use when drafting or editing READMEs, guides, reference documentation, or other technical prose.

16 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

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

  • 0

    Common

    Most of the 13 edited versions we read keep these.

  • 5

    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:

    Use practical ASD-STE100 principles, not strict compliance.

    line 8
  2. Distinctive:

    Write short sentences with one main idea each.

    line 12
  3. Distinctive:

    Use active voice and imperative verbs for instructions.

    line 13
  4. Distinctive:

    Prefer familiar words and consistent terms.

    line 14
  5. Distinctive:

    Remove repetition only when meaning and scope stay unchanged.

    line 16

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

Clear Writing

Use practical ASD-STE100 principles, not strict compliance.

Language rules

  • Write short sentences with one main idea each.
  • Use active voice and imperative verbs for instructions.
  • Prefer familiar words and consistent terms.
  • Replace vague references with explicit names.
  • Remove repetition only when meaning and scope stay unchanged.

Preserve meaning

Preserve requirements, prohibitions, exceptions, conditions, instruction priority, and technical terms. Keep existing code, commands, paths, and identifiers unchanged unless explicitly asked to change them. Flag ambiguity instead of guessing.

Follow the requested task

Draft new documents, revise existing text, or report suggestions as requested. Do not impose a review-only workflow. Skip changes that do not improve clarity.

Example

Original: "Once the installation process has been completed, you should then proceed to restart the server."

Clearer: "After installation finishes, restart the server."

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.