agentleFS
Sign inStart free
VercelKnown publishervercel-labs/typefully-eve-template/agent/skills/writing-quality/SKILL.md

writing-quality

Skill8 starsChanged 21 days agoMITView on GitHub

Generic writing-quality rules for any prose meant for humans to read: keep it natural, plain, and free of AI-sounding phrasing, and check it against the AI-phrases and plain-English reference lists. Load before drafting, editing, or reviewing content. Not needed for code or configuration work.

9 other projects use a version of this, 4 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 9 edited versions we read keep these.

  • 0

    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:

    Prefer plain English. Swap bloated or vague wording for the shorter, concrete alternative.

    line 18

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

House-neutral rules for making prose read like a person wrote it, and for judging whether it does. They apply to any surface: a social post, a Notion page, a thread, release notes. Platform- or brand-specific voice guidance layers on top of them.

When to Apply

Load this skill before:

  • Drafting new content
  • Editing or rewriting existing content
  • Reviewing a draft

Core Rules

  1. Kill the AI tells: em-dash overuse, "delve", "leverage", "it's not just X, it's Y", rule-of-three padding, and the rest of the patterns in references/ai-phrases-to-avoid.md.
  2. Prefer plain English. Swap bloated or vague wording for the shorter, concrete alternative. references/plain-english-alternatives.md is the lookup table.
  3. Front-load the point. Lead sentences, paragraphs, and sections with the conclusion, because readers scan.
  4. Concrete over abstract. Show an example before stating a principle, and cut hedges like "just", "simply", "very", and "really".
  5. Match the user's voice, not a default. When working with existing content, keep its register and conventions. These rules trim the noise; they don't impose a personality.

References

  • references/ai-phrases-to-avoid.md: words, phrases, and punctuation patterns that mark text as AI-generated, with replacements.
  • references/plain-english-alternatives.md: plain-English swaps for corporate, padded, or vague wording.

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.

Check your setup, free