Resume Proofreader
Proofreads resume, CV and cover-letter drafts for grammar, clarity, consistency and...
Install
npx skills add reactive-resume/reactive-resume --skill resume-proofreader -g -a claude-code -y- Repository
- reactive-resume/reactive-resume45.2k
- Category
- Media
- Updated
- 3d ago
- License
- MIT
- Context cost
- Lightabout 854 tokens
- Runs scripts
- No, instructions only
What it does
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.
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
- 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.
- 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.
- 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.
- 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.
- 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.
