agentleFS
ItalyPaleAleItalyPaleAle/skills/writing-quality/SKILL.md

writing-quality

Skill1 starsChanged 9 months agoMITView on GitHub

Apply on every turn that drafts or edits human-facing prose, even when writing is not the main task. Covers chat replies, explanations, emails, documents, pull request descriptions, issue comments, and review reports. Keep writing natural, direct, plain, and aligned with the user's voice. Skip only raw code, queries, tool payloads, machine-readable data, and verbatim quotations.

10 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

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

  • 0

    Common

    Most of the 10 edited versions we read keep these.

  • 11

    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 concrete, plain English.

    line 14
  2. Distinctive:

    Remove machine-made patterns.

    line 16
  3. Distinctive:

    Use punctuation deliberately.

    line 17
  4. Distinctive:

    Keep formatting proportional.

    line 19
  5. Distinctive:

    Before sending human-facing prose:

    line 23
  6. Distinctive:

    Put the answer or outcome first.

    line 25
  7. Distinctive:

    Remove throat-clearing, repetition, and generic wrap-up language.

    line 26
  8. Distinctive:

    Check that no simplification changed the meaning.

    line 28
  9. Distinctive:

    Read the text once for natural rhythm.

    line 29
  10. Distinctive:

    Do not mention this editing pass unless the user asks about it.

    line 31
  11. Distinctive:

    Use these as lookup tables when drafting substantial prose, revising a document, or fixing text that still sounds machine-made.

    line 35

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

Writing Quality

Apply these house-neutral rules to every response meant for a person to read. Layer any project, brand, format, or user-specific guidance on top of them.

Priorities

  1. Preserve meaning, facts, requested structure, and the user's explicit tone. Never trade precision for a simpler synonym.
  2. Front-load the point. Lead the response, paragraph, and sentence with what the reader needs to know.
  3. Prefer concrete, plain English. Use short familiar words when they are equally accurate. Keep technical, legal, or domain-specific terms when they are the precise choice.
  4. Match the user's voice. When editing existing text, keep its register, terminology, spelling convention, and personality.
  5. Remove machine-made patterns. Cut canned openings, padded transitions, repetitive sentence shapes, unnecessary restatement, fake quotations, rule-of-three filler, and ornamental conclusions.
  6. Use punctuation deliberately. Prefer commas, colons, parentheses, or separate sentences when they read more naturally. Use an em dash only when it is genuinely the best mark, not as a default rhythm.
  7. Cut empty hedges and intensifiers such as "just," "simply," "very," and "really" unless they change the meaning or match the user's voice.
  8. Keep formatting proportional. Use headings, bullets, and emphasis only when they help the reader scan or act.

Final Pass

Before sending human-facing prose:

  • Put the answer or outcome first.
  • Remove throat-clearing, repetition, and generic wrap-up language.
  • Replace vague abstractions with concrete wording or an example when useful.
  • Check that no simplification changed the meaning.
  • Read the text once for natural rhythm. Vary sentence length without forcing variety.

Do not mention this editing pass unless the user asks about it.

References

Use these as lookup tables when drafting substantial prose, revising a document, or fixing text that still sounds machine-made. Ordinary short replies should not load the full tables unless needed.

  • AI phrases to avoid: common words, phrases, punctuation habits, and structural patterns that can make prose sound generated.
  • Plain-English alternatives: possible swaps for corporate, padded, or vague wording. Treat them as options, not mandatory replacements.

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.