proofread
/proofread
Proofread papers and manuscripts. Checks grammar, typos, layout, consistency, writing quality. Produces report without editing files. Use when finding surface-level errors, not substantive academic critique.
- Author
- felpix-studios ↗
- Repository
- social-science-research ↗
- Licence
- MIT
- Last repository change
- 06.07.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 06.07.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Proofread papers and manuscripts. Checks grammar, typos, layout, consistency, writing quality. Produces report without editing files. Use when finding surface-level errors, not substantive academic critique.
Arguments
/proofread [filename, 'all', or path to manuscript]
Original author description
Proofread papers and manuscripts. Checks grammar, typos, layout, consistency, writing quality. Produces report without editing files. Use when finding surface-level errors, not substantive academic critique.
How it works
- Steps
SKILL.md preview
---
name: proofread
description: "Proofread papers and manuscripts. Checks grammar, typos, layout, consistency, writing quality. Produces report without editing files. Use when finding surface-level errors, not substantive academic critique."
when_to_use: "proofread, check typos, grammar check, look for errors, proofread all, polish this, check my writing, any mistakes, proofread before sending, clean-up pass"
argument-hint: "[filename, 'all', or path to manuscript]"
allowed-tools: ["Read", "Grep", "Glob", "Write", "Task", "AskUserQuestion"]
---
# Proofread Academic Writing
Run the mandatory proofreading protocol on papers or manuscripts. Produces a report of all issues WITHOUT editing any source files.
## Steps
1. **Identify files to review:**
- If `$ARGUMENTS` is a specific filename: review that file only
- If `$ARGUMENTS` is `all`: review all files in `manuscripts/` and `Quarto/` (if it exists)
- If `$ARGUMENTS` is a file in `manuscripts/`: treat as manuscript (not slides)
- If `$ARGUMENTS` is empty or ambiguous and multiple files exist, use AskUserQuestion:
- header: "Files"
- question: "Which files should I proofread?"
- multiSelect: true
- options: list up to 4 found files (label: filename, description: directory and file type). User can select multiple or choose "Other" to specify a path.
2. **For each file, launch the `proofreader` agent** (via Task). It checks grammar, typos, layout issues, consistency, and academic quality — the agent definition owns the full category specifications, so do not restate them here.
3. **Produce a detailed report** for each file listing every finding with:
- Location (line number or section heading)
- Current text (what's wrong)
- Proposed fix (what it should be)
- Category and severity
4. **Save each report** to `quality_reports/`:
- For `.tex` slide files: `quality_reports/FILENAME_report.md`
- For `.qmd` slide files: `quality_reports/FILENAME_qmd_report.md`
- For manuscript files: `quality_reports/FILENAME_proofread.md`
5. **IMPORTANT: Do NOT edit any source files.**
Read `${CLAUDE_PLUGIN_ROOT}/skills/proofread/references/proofreading-protocol.md`. Only produce the report. Fixes are applied separately after user review.
6. **Present summary** to the user:
- Total issues found per file
- Breakdown by category
- Most critical issues highlighted
Files in this package (2)
- SKILL.md 2 KB
- references/proofreading-protocol.md 1 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · felpix-studios/social-science-research | 90 | MIT |
| Cavalry-Collective/visual-stack | 100 | MIT |
| kikearciniegas/proofread | 100 | MIT |
| sonilo-ai/skills | 100 | MIT |
| scratchpad-sh/skills | 100 | MIT |
| tance-mang/chinese-webnovel-skills | 100 | MIT |
| pedrohcgs/claude-code-my-workflow | 90 | MIT |
Database snapshot: 13.11.2026 · package version 64ceadac1c50 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100content-proofreading
An academic proofreading skill for Chinese/English manuscripts, triggered when you need automated checks for spelling, grammar, terminology consistency, and formatting before submission. - 100proof
Use when the user asks for proofreading or light copy editing while preserving original wording, tone, and order. Triggers: 'proofread', 'fix typos', 'grammar only', 'copy edit only', 'SPAG pass'. Not for rewrites, tone shifts, structural edits, or style upgrades; use… - 100cmd-write-proofread
Proofread posts before publishing for spelling, grammar, syntax, punctuation, word usage, repetition, logic, weak arguments, clarity, structure, broken links, and image/text consistency. Use this whenever a user asks to proofread, edit, review, or improve a post, essay, article,… - 100paper-polishing
Language polishing — Academic English paper polishing for LaTeX manuscripts. Polishes grammar, word choice, sentence structure, logic flow, and academic tone while preserving all LaTeX markup (verified by a placeholder round-trip protocol); does NOT judge scientific content (use… - 90proofread-document
Hunt typos and language errors in a LaTeX/markdown document — spelling, doubled or missing words, subject/verb agreement, punctuation, quotes, unescaped LaTeX characters, and inconsistent hyphenation or capitalization of repeated terms. Reports each finding with its line and an… - 100proofread-math
Conservatively proofread mathematical prose and LaTeX for grammar, typography, syntax, notation consistency, cross-references, and uniquely forced local mathematical typos. Use for explicit math-proofreading requests and final self-review of theorem-, proof-, or equation-heavy…