# Resume Proofreader

Proofreads resume, CV and cover-letter drafts for grammar, clarity, consistency and...

- Repository: https://github.com/reactive-resume/reactive-resume (45160 stars)
- Category: Media
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add reactive-resume/reactive-resume --skill resume-proofreader -g -a claude-code -y`
Codex: `npx skills add reactive-resume/reactive-resume --skill resume-proofreader -g -a codex -y`
Cursor: `npx skills add reactive-resume/reactive-resume --skill resume-proofreader -g -a cursor -y`
Gemini CLI: `npx skills add reactive-resume/reactive-resume --skill resume-proofreader -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add reactive-resume/reactive-resume`

## Description

Proofreads resume, CV and cover-letter drafts for grammar, clarity, consistency and unsupported wording while preserving facts and voice. Use for a final editorial pass or a bounded wording fix; use resume-content-guide for section selection and resume-tailor for job matching.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Resume Proofreader

Use the user's evidence, never facts or numbers from worked examples. If asked to fabricate or inflate a claim, decline that part briefly, offer the strongest truthful version and complete the remaining work; maintain that boundary if pressed.

Polish the supplied draft without changing the person's history. A one-line request gets a one-line edit; a full-document request gets the passes below. Work from text or files without requiring an account.

## Editing passes

1. **Meaning and facts.** Record titles, dates, names, amounts, units, qualifiers and credential status before editing. Flag contradictions against supplied material. Do not turn “helped” into “led,” “about” into an exact figure, or a draft paper into a publication.
2. **Clarity.** Replace vague filler with the existing concrete action. Split overloaded sentences. Keep necessary domain terms; spell out an acronym where the intended reader needs it. If explaining a result needs a fact the user has not supplied, ask instead of supplying it.
3. **Consistency.** Align tense, punctuation, spelling variety and date presentation. Completed achievements in a current job can be past tense. Standardize how a date is displayed without inventing missing months. Different countries' spellings are not errors.
4. **Voice and economy.** Remove repetition, inflated adjectives and generic claims while retaining the user's phrasing where it works. Do not add intentional errors, odd synonyms or claims about defeating AI detectors.
5. **Final comparison.** Confirm every edit preserves the action, attribution and degree of certainty. Recheck headings, links as written, duplicate entries and unfinished placeholders. An unfamiliar proper noun is a question, not an automatic correction.

The rest: https://github.com/reactive-resume/reactive-resume/blob/HEAD/plugins/reactive-resume/skills/resume-proofreader/SKILL.md