Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
pedrohcgs avatar

Proofread

  • 54 installs
  • 1.4k repo stars
  • Updated June 10, 2026
  • pedrohcgs/claude-code-my-workflow

Helps with ai & agent building tasks.

About

proofread is a Claude Code skill for ai & agent building. It helps solo builders move faster with AI-assisted development.

  • proofread
  • AI & Agent Building
  • AI-coding skill

Proofread by the numbers

  • 54 all-time installs (skills.sh)
  • +4 installs in the week ending Aug 4, 2026 (Skillselion tracking)
  • Ranked #6,877 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/pedrohcgs/claude-code-my-workflow --skill proofread

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs54
repo stars1.4k
Last updatedJune 10, 2026
Repositorypedrohcgs/claude-code-my-workflow

What it does

Helps with ai & agent building tasks.

Files

SKILL.mdMarkdownGitHub ↗

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

Related skills

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.