Proofread Skill for Claude
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.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/pedrohcgs/claude-code-my-workflow --skill proofreadThe instruction itself
2 sections, as written by the authorProofread Lecture Files
Run the mandatory proofreading protocol on lecture files. This produces a report of all issues found WITHOUT editing any source files.
Steps
- Identify files to review:
- If
$ARGUMENTSis a specific filename: review that file only - If
$ARGUMENTSis "all": review all lecture files inSlides/andQuarto/
- 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
- 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
- Save each report to
quality_reports/: - For
.texfiles:quality_reports/FILENAME_report.md - For
.qmdfiles:quality_reports/FILENAME_qmd_report.md
- IMPORTANT: Do NOT edit any source files.
Only produce the report. Fixes are applied separately after user review.
- Present summary to the user:
- Total issues found per file
- Breakdown by category
- Most critical issues highlighted
Other skills for the same job
different authors, same section of the catalogue
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
Use when implementing any feature or bugfix, before writing implementation code
Use when you have a spec or requirements for a multi-step task, before touching code
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Use when writing or improving README files. Not all READMEs are the same — provides templates and guidance matched to your audience and project type.
| Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, negative parallelisms, and excessive conjunctive phrases.
Official Opentrons Protocol API for OT-2 and Flex robots. Use when writing protocols specifically for Opentrons hardware with full access to Protocol API v2 features. Best for production Opentrons protocols, official API compatibility. For multi-vendor automation or broader equipment control use pylabrobot.
How to use it
Take pedrohcgs/proofread from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.