Read-only proofreading pass over lecture `.tex` or `.qmd` files. Checks grammar, typos, overflow, terminology consistency, and academic writing quality; produces a report without editing. Use when user says "proofread", "check for typos", "look for grammar issues", "copy-edit this", "any writing errors?", or before a lecture release.
Scanned 6/11/2026
Install to Claude Code
npx -y skills add pedrohcgs/claude-code-my-workflow --skill proofread --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Proofread?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/pedrohcgs-proofread)More formats (shields.io, HTML) on the badges page.
---
name: proofread
description: Read-only proofreading pass over lecture `.tex` or `.qmd` files. Checks grammar, typos, overflow, terminology consistency, and academic writing quality; produces a report without editing. Use when user says "proofread", "check for typos", "look for grammar issues", "copy-edit this", "any writing errors?", or before a lecture release.
argument-hint: "[filename or 'all']"
allowed-tools: ["Read", "Grep", "Glob", "Write", "Task"]
---
# Proofread Lecture Files
Run the mandatory proofreading protocol on lecture files. This produces a report of all issues found 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 lecture files in `Slides/` and `Quarto/`
2. **For each file, launch the proofreader agent** that checks for:
**GRAMMAR:** Subject-verb agreement, articles (a/an/the), prepositions, tense consistency
**TYPOS:** Misspellings, search-and-replace artifacts, duplicated words
**OVERFLOW:** Overfull hbox (LaTeX), content exceeding slide boundaries (Quarto)
**CONSISTENCY:** Citation format, notation, terminology
**ACADEMIC QUALITY:** Informal language, missing words, awkward constructions
3. **Produce a detailed report** for each file listing every finding with:
- Location (line number or slide title)
- Current text (what's wrong)
- Proposed fix (what it should be)
- Category and severity
4. **Save each report** to `quality_reports/`:
- For `.tex` files: `quality_reports/FILENAME_report.md`
- For `.qmd` files: `quality_reports/FILENAME_qmd_report.md`
5. **IMPORTANT: Do NOT edit any source files.**
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
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!