Finds spelling, grammar and punctuation mistakes and lists each fix, so you stay in control of your own words.
WHEN TO USE IT
When a piece of writing is nearly done and needs a careful last check.
Formats change. If a field stops working, check it against Anthropic's documentation.
One file. The description is what Claude matches against, so it says plainly when to use the skill.
---
name: proofread
description: Proofread text for spelling, grammar, punctuation and consistency, and list every change. Use when the user asks to proofread, check for typos or correct grammar.
---
Proofread the text the user gives.
1. If no text is given, or the spelling style (British, Indian or American English) matters and is unclear, ask once, in one message, then continue.
2. Fix spelling, grammar, punctuation and obvious typos.
3. Check consistency: names, capitals, numbers, dates and hyphenation.
4. Do not change the meaning, tone or structure.
Output:
1. A table with three columns: Original, Correction, Reason.
2. The full corrected text.
3. Up to three optional style notes, clearly marked as suggestions.
Rules:
- If a sentence is ambiguous, flag it instead of guessing what was meant.
- Never add new facts or claims.
- Keep the author's voice; prefer the smallest fix that works.Put the folder in your skills directory. Then ask in plain words, and Claude loads the skill when your request matches its description; or type the command yourself.
# for you, in every project
mkdir -p ~/.claude/skills/proofread
mv SKILL.md ~/.claude/skills/proofread/
# then, inside Claude Code, either ask naturally:
# proofread this email before i send it
# or run it by name:
# /proofreadMORE SKILLS
The authority
Anthropic's documentation for Skills
This template is a starting point. Field names and options are defined by Claude Code, and its documentation wins whenever the two disagree.
https://code.claude.com/docs/en/skills