mcpbeat Sign in

Writing Quality Agent Skill

Writing-quality guardrails for any prose the agent drafts or edits: blog posts, page copy, Notion drafts, release notes, marketing text. Use this skill whenever writing or revising content meant for humans to read, to keep the prose natural, plain, and free of AI-sounding phrasing. Not needed for code, queries, or structural CMS work.

6k tokens
context cost
the whole folder, loaded on every use
5
files
instructions only
0
copies elsewhere
how many repositories repackaged it
2
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/vercel-labs/typefully-eve-template --skill writing-quality

What comes with it

23 241 bytes besides the instruction
references/ai-phrases-to-avoid.md
references/plain-english-alternatives.md
references/web-content-specs.md
references/web-writing-best-practices.md

What it tells the agent to use

found in the instruction text
Read reads your files

The instruction itself

4 sections, as written by the author

Writing Quality

House-neutral rules for making drafted content read like a person wrote it. They apply to any prose surface. Layer project- or brand-specific voice guidance on top of them.

When to Apply

Load this skill before:

  • Drafting new content (a blog post, landing-page copy, a Notion draft, release notes)
  • Editing or rewriting existing content
  • Reviewing a draft before proposing it to the user

Core Rules

  • 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.
  • Prefer plain English. Swap bloated or vague wording for the shorter, concrete alternative. references/plain-english-alternatives.md is the lookup table.
  • Front-load the point. Lead sentences, paragraphs, and sections with the conclusion, because readers scan.
  • Concrete over abstract. Show an example before stating a principle, and cut hedges like "just", "simply", "very", and "really".
  • Match the user's voice, not a default. When editing existing content, keep its register and conventions. These rules trim the noise; they don't impose a personality.

References

Load the reference that matches the task 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. Load when drafting or editing any prose.
  • references/plain-english-alternatives.md: plain-English swaps for corporate, padded, or vague wording. Load when drafting or editing any prose.
  • references/web-writing-best-practices.md: a sourced checklist for long-form web content, covering scanning behavior, hooks, structure, readability, length by intent, SEO basics, and closes. Load when writing or restructuring articles, blog posts, or guides.
  • 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). Load for a final spec check on a piece. Title, meta, and Open Graph specs live in the seo-aeo-best-practices skill.

How to use it

Copy the folder

Take vercel-labs/writing-quality from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.