Professional proofreader
Skill sinhoneyy/master-skills/skills/professional-proofreader
Unified skill library for Claude, Codex, Cursor, Antigravity & AI agents — 2,658 skills across 15 domains
npx -y skills add sinhoneyy/master-skills --skill professional-proofreaderAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 9 stars9 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use when a user asks to "proofread", "review and correct", "fix grammar", "improve readability while keeping my voice", and to proofread a document file and save an updated version.
SKILL.md
3.0 KB, as published. Nobody here has run it
Professional Proofreader
Overview
This skill transforms flawed writing — whether pasted text or uploaded documents — into publication-ready prose without altering the author’s intent. It eliminates grammatical, spelling, punctuation, clarity, and tone issues while strictly preserving the author’s voice and intent. Returns a corrected version plus a structured modification log, or generates an updated file when requested. Not for code editing or technical refactoring.
When to Use
- Use when user asks to "proofread", "review and correct", "fix grammar", "polish this text", "improve readability while keeping my voice".
- Use when user asks to proofread a document file (like .docx, .pdf, .txt) and save the updated version as new file with 'UPDATED_' prefix.
WORKFLOW MODES
This skill operates in two modes:
- Inline Text Mode
- File Processing Mode
MODE 1: Inline Text
Refer markdown for complete inline text mode.
MODE 2: File Processing
Trigger when user says:
- "Proofread [filename].[extension]
- "Edit this document"
- "Correct grammar in this file"
- "Save updated version"
- "Add prefix UPDATED_"
- "Return corrected .[extension]"
Refer markdown for complete file processing mode.
Best Practices
✅ Do: [Good practice]
- Always include modification explanations.
- Always keep quality standards equivalent to: Academic proofreading, business document refinement, pre-publication review.
- Always follow below editing standards:
Grammar
- Subject-verb agreement
- Tense consistency
- Article usage
- Prepositions
- Pronoun clarity
Spelling
- Correct typos
- Maintain original spelling variant (US/UK)
Punctuation
- Commas
- Apostrophes
- Quotation marks
- Sentence boundaries
Style & Tone
- Maintain author voice
- Avoid unnecessary formalization
- Preserve rhetorical choices
Readability
- Improve structure
- Enhance logical flow
- Remove redundancy
❌ Don't: [What to avoid]
- Never alter meaning.
- Never drop formatting intentionally.
- Never change file name logic beyond request.
- Never expand the content
Output Rules
If inline: -> Return Corrected Version + Modifications list.
If file rewrite: -> Save updated file. -> Confirm filename. -> Provide modifications list unless suppressed.
Give friendly message to user in the end.
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.