mcpbeat

Content Editing

vercel-labs/content-editing

Use before handing back any long-form draft: edit in separate passes for sense, voice, reader payoff, proof, and specificity rather than re-reading and tweaking.

2k tokens
context cost
the whole folder, loaded on every use
3
files
instructions only
0
copies elsewhere
how many repositories repackaged it
359
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/marketing-team-eve-template --skill content-editing

What comes with it

4 396 bytes besides the instruction
references/common-problems.md
references/editing-checklist.md

The instruction itself

1 sections, as written by the author

Content editing

Edit in passes, one dimension at a time. Re-reading a draft looking for everything at once finds nothing; each pass below has a single question. After a pass, check you haven't broken an earlier one.

  • Does it make sense? Find the sentences carrying two ideas, the pronouns with no clear referent, the jargon a reader outside the company wouldn't know, and the point buried under qualifications. Fix structure before wording.
  • Does it sound like us? One voice throughout. Watch for the register slipping into corporate abstraction in the middle sections, which is usually where the writer got bored. Check against the brand context's voice, not your own defaults.
  • Does the reader care? For each section, ask what the reader gets from it. A feature described without a consequence fails this pass: say what it lets them do or cut it. If the answer is "it's context", it's probably too long.
  • Is it proven? Every claim needs a number, a source, a named example, or an explicit hedge. Mark the ones that have none. You are not verifying them here, you're finding them: flag what needs a source rather than softening it into vagueness.
  • Is it specific? Replace the general with the concrete. "Significantly faster" becomes the measured figure; "many teams" becomes the count you can support; "leading companies" becomes names you have permission to use. If you can't get the specific, drop the claim rather than keeping the vague version.

Then the mechanical pass: cut hedges and filler, break up sentences over about 25 words, kill passive voice where an actor exists, make sure each paragraph opens on its own point, and check the opening earns the second sentence.

Read references/editing-checklist.md for the pass-by-pass checks, and references/common-problems.md for the recurring failure patterns and their fixes.

This skill is about structure and argument. writing-quality carries the word-level rules, the AI phrases to avoid, and the plain-English list; load both.

How to use it

Copy the folder

Take vercel-labs/content-editing 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.