Professional proofreader

Skill sickn33/agentic-awesome-skills/plugins/agentic-awesome-skills/skills/professional-proofreader

AAS Core is the local, agent-first control plane for complete catalog discovery, agent-owned selection, stack validation, and planning, backed by 1,987+ agentic skills. Includes CLI, local MCP, catalog, plugins, and Workbench.

Install

npx -y skills add sickn33/agentic-awesome-skills --skill professional-proofreader

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

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.