proofread — Claude Code skill: lecture proofing without edits
Runs a proofreading pass over .tex and .qmd lecture files and hands back a report. Source files stay untouched.
npx skills add pedrohcgs/claude-code-my-workflow --skill proofread -a claude-codeWhat proofread does
Point the skill at one file or at everything: the argument takes a filename or the word all, which sweeps the Slides/ and Quarto/ folders.
Five checks run per file: grammar (agreement, articles, prepositions, tense), typos and leftover search-and-replace damage, overflow (overfull hbox in LaTeX, content spilling past slide edges in Quarto), consistency of citations, notation and terminology, plus academic writing quality. A proofreader subagent handles each file.
Reports land in quality_reports/ — quality_reports/FILENAME_report.md for .tex, quality_reports/FILENAME_qmd_report.md for .qmd. Each finding lists its location, the current text, a proposed fix, a category and a severity. You apply the fixes yourself once you have read through the report. Edit and MultiEdit are disallowed for this skill, so it cannot rewrite a lecture behind your back.
What it helps with
- catch typos and search-and-replace artifacts before a lecture ships
- spot overfull hbox warnings ahead of a LaTeX build
- keep terminology and citation format aligned across a whole course
- proof an entire slide deck set in one pass instead of file by file
- get a fix list while leaving the sources alone
Example prompts for the agent
- Proofread
lecture03.texand show me the report - Check every lecture for typos and overflow:
all - Look for grammar issues in
Quarto/intro.qmd
How to install proofread
1Skills CLI (Vercel)
npx skills add pedrohcgs/claude-code-my-workflow --skill proofread -a claude-code2Manually: put the files in place
~/.claude/skills/proofread/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/proofread/
1Skills CLI (Vercel)
npx skills add pedrohcgs/claude-code-my-workflow --skill proofread -a codex2Manually: put the files in place
.agents/skills/proofread/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add pedrohcgs/claude-code-my-workflow --skill proofread -a cursor2Manually: put the files in place
.cursor/skills/proofread/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install pedrohcgs/claude-code-my-workflow proofread2Manually: put the files in place
.github/skills/proofread/SKILL.md1Skills CLI (Vercel)
npx skills add pedrohcgs/claude-code-my-workflow --skill proofread -a gemini-cli2Platform CLI
gemini skills install https://github.com/pedrohcgs/claude-code-my-workflow --path .claude/skills/proofreadManually: put the files in place
.devin/skills/proofread/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add pedrohcgs/claude-code-my-workflow --skill proofread -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about proofread
How do I install proofread in Claude Code?
Run npx skills add pedrohcgs/claude-code-my-workflow --skill proofread -a claude-code. The skill file ends up at ~/.claude/skills/proofread/SKILL.md.
What does proofread do?
It reads lecture .tex or .qmd files and writes a report covering grammar, typos, overflow, terminology drift and weak academic phrasing. The source files are left as they were.
Can the skill apply the fixes itself?
No. Edit and MultiEdit sit on its disallowed list, so all it does is write a report into quality_reports/. You make the changes after reviewing it.
Source text
SKILL.md · MIT
--- 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", "Agent", "Task"] disallowed-tools: ["Edit", "MultiEdit"] --- # Proofread Lecture Files Run the 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. **Leave source files unchanged** — fixes are applied after the user reviews the report. 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
© pedrohcgs · MIT · pedrohcgs/claude-code-my-workflow
