Claude Skill

proofread

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 thi

LLM Mart · 0 points · 1 views 0 listing impressions 0 install-command copies
Download pedrohcgs-claude-code-my-workflow-.claude_skills_proofread-fe70774.zip · 1 KB

Install

skills CLI npx skills add https://github.com/pedrohcgs/claude-code-my-workflow/tree/main/.claude/skills/proofread
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install pedrohcgs-claude-code-my-workflow@llmmart
Git git clone https://github.com/pedrohcgs/claude-code-my-workflow.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole pedrohcgs/claude-code-my-workflow collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

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
Files (claude-code-my-workflow)
  • SKILL.md 2 KB
    ---
    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
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.