← LeaderboardThe Skill Leaderboard

proofread

Run the proofreading protocol on lecture files. Checks grammar, typos, overflow, consistency, and academic writing quality. Produces a report without editing files.

Published by brycewang-stanford ↗brycewang-stanford/Auto-Empirical-Research-Skills

Try your first task

proofread

Start a fresh conversation. Replace the highlighted placeholders.

Use proofread to review [file or all] lecture files and produce detailed, non-editing quality reports covering grammar, typos, overflow, consistency, and academic quality, with locations, proposed fixes, severity, and a summary.

Required inputs

  • [file or all]

User-approved starter prompt based on a pinned source version; check current skill requirements before running. Task evidence ↗

SKILL.md

name: proofreaddescription: Run the proofreading protocol on lecture files. Checks grammar, typos, overflow, consistency, and academic writing quality. Produces a report without editing files.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