agentleFS
VercelKnown publishervercel/eve/apps/templates/sanity-copilot-eve-template/agent/subagents/reviewer/skills/writing-quality/SKILL.md

writing-quality

Skill5.9k starsChanged 4 days agoApache-2.0View on GitHub

The review rubric: writing-quality rules and reference lists for judging a content draft, covering AI-sounding phrasing, bloated wording, structure, and web-content specs. Load at the start of every review.

10 other projects use a version of this, 3 of them edited.

Trending

More talk lately.about the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 0 mentionsApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 7 mentionsJul 2026: 11 mentionsAug 2026: 7 mentionsSep 2026: 10 mentionsOct 2026: 16 mentionsNov 2026: 6 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the vercel/eve repository that our weekly crawl found. There is no adoption data for this file yet.

Most recently taken up by

Who's talking about vercel/eve

The biggest 5 of 57 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 57

Talked about on GitHub and Bluesky (57 times).

On GitHub · 50

45 more on GitHub

On Bluesky · 7

2 more on Bluesky

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 15

“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 judging whether drafted content reads like a person wrote it. They apply to any prose surface. Voice or audience context from the caller layers on top of them.

When to Apply

Load this skill at the start of every review, before reading the 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 judging edits to existing content, respect its register and conventions. These rules trim the noise; they don't impose a personality.

References

Load the reference that matches the draft rather than all of them at once:

  • references/ai-phrases-to-avoid.md: words, phrases, and punctuation patterns that mark text as AI-generated, with replacements. Applies to every review.
  • references/plain-english-alternatives.md: plain-English swaps for corporate, padded, or vague wording. Applies to every review.
  • references/web-writing-best-practices.md: a sourced checklist for long-form web content, covering scanning behavior, hooks, structure, readability, length by intent, and closes. Apply when the draft is an article, blog post, or guide.
  • references/web-content-specs.md: the concrete numbers behind that checklist (slug rules, heading cadence, readability thresholds, word count by intent, alt text, internal links). Apply for a final spec check on long-form pieces.

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.