接続

Professional Proofreader

sickn33bysickn33
•
35k
•
コンテンツ管理

Refines written content by correcting grammar, spelling, and readability while strictly preserving the author's original voice and intent.

The Professional Proofreader skill transforms flawed writing into publication-ready prose across both inline text and local document files. It provides a comprehensive linguistic review—addressing subject-verb agreement, tense consistency, punctuation, and structural flow—without altering the core meaning or unique rhetorical choices of the writer. Designed for academic, business, and creative contexts, it offers automated file processing with version tracking and provides detailed modification logs to ensure every correction is transparent and intentional.

主な機能

0135,078 GitHub stars
02Automated document file processing with 'UPDATED_' prefixing
03Detailed modification logs for every edit made
04Comprehensive grammar, spelling, and punctuation correction
05Support for regional spelling variants (US/UK English)
06Preservation of authorial voice and rhetorical intent

ユースケース

01Polishing business reports and professional emails for clarity and tone
02Bulk proofreading local document files with automated version control
03Reviewing academic manuscripts or documentation prior to publication
name professional-proofreader
description 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.
risk safe
source original
date_added 2026-03-04

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.

Example

User request:

Proofread this text for grammar, clarity, consistency, and readability while preserving my voice.

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.