agentleFS
NzettodessNzettodess/Awesome-Agent-Skills/Skills/Writing/professional-proofreader/SKILL.md

professional-proofreader

Skill0 starsChanged 6 months agoMITView on GitHub

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.

2 other projects use a version of this, 2 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

11 rules. About 0 are common, 11 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈11

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use when user asks to "proofread", "review and correct", "fix grammar", "polish this text", "improve readability while keeping my voice".

    line 21
  2. Distinctive:

    Use when user asks to proofread a document file (like .docx, .pdf, .txt) and save the updated version as new file with 'UPDATED_' prefix.

    line 22
  3. Distinctive:

    Always include modification explanations.

    line 54
  4. Distinctive:

    Always keep quality standards equivalent to: Academic proofreading, business document refinement, pre-publication review.

    line 55
  5. Distinctive:

    Always follow below editing standards:

    line 56
  6. Distinctive:

    Never drop formatting intentionally.

    line 87
  7. Distinctive:

    Never change file name logic beyond request.

    line 88
  8. Distinctive:

    Never expand the content

    line 89
  9. Distinctive:

    Use this skill only when the task clearly matches the scope described above.

    line 108
  10. Distinctive:

    Do not treat the output as a substitute for environment-specific validation, testing, or expert review.

    line 109
  11. Distinctive:

    Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

    line 110

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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:

  1. Inline Text Mode
  2. 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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.