proofread
Checks LaTeX documents for errors and quality issues without changing any files.
Install
mkdir -p .claude/skills/proofread && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/14329" && unzip -o skill.zip -d .claude/skills/proofread && rm skill.zipInstalls to .claude/skills/proofread
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Proofread a LaTeX document for grammar, typos, notation consistency, and academic writing quality. Produces a report without editing files.Key capabilities
- →Identify files to review based on arguments
- →Check LaTeX files for grammar issues
- →Check LaTeX files for typos
- →Check LaTeX files for notation consistency
- →Check LaTeX files for LaTeX syntax issues
- →Check LaTeX files for academic writing quality
How it works
The skill identifies specified LaTeX files, then systematically checks each file for grammar, typos, notation, LaTeX syntax, and academic quality issues, compiling a detailed report without modifying the original files.
Inputs & outputs
When to use proofread
- →Checking academic paper drafts
- →Ensuring notation consistency in LaTeX
- →Reviewing technical documentation
About this skill
Proofread LaTeX Files
Run the proofreading protocol on LaTeX files. 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.texfiles in the current directory
- If
-
For each file, check for:
GRAMMAR: Subject-verb agreement, articles (a/an/the), tense consistency (present for established results, past for "we showed") TYPOS: Misspellings, duplicated words, search-and-replace artifacts NOTATION: Consistent use of $\mathbb{F}_p$, $\mathcal{A}$, $\lambda$; variables introduced before use; quantifiers explicit LATEX: Missing
~before\cite/\ref,\left/\rightmismatches, mismatched environments ACADEMIC QUALITY: Informal language, vague claims ("it is clear that..."), missing words -
Produce a report listing every finding with:
- Line number
- Current text
- Proposed fix
- Category and severity
-
IMPORTANT: Do NOT edit any source files. Only produce the report.
-
Present summary to the user:
- Total issues per file
- Breakdown by category
- Most critical issues highlighted
Adapted from pedrohcgs/claude-code-my-workflow (MIT license).
When not to use it
- →When direct editing of source files is required
- →When the document is not a LaTeX file
Limitations
- →Does NOT edit any source files
- →Only produces a report of findings
How it compares
This skill provides a structured, non-invasive proofreading protocol for LaTeX documents, generating a complete report of issues without altering the source, unlike manual editing or tools that automatically apply fixes.
Compared to similar skills
proofread side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| proofread (this skill) | 0 | 5mo | No flags | Beginner |
| writing-clearly-and-concisely | 3 | 6mo | No flags | Beginner |
| professional-proofreader | 0 | 2mo | No flags | Beginner |
| writing-style | 0 | 2mo | No flags | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
writing-clearly-and-concisely
davila7
Use when writing prose humans will read—documentation, commit messages, error messages, explanations, reports, or UI text. Applies Strunk's timeless rules for clearer, stronger, more professional writing.
professional-proofreader
diegosouzapw
Professional Proofreader workflow skill. Use this skill when the user needs > and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
writing-style
xpcoffee
Use when drafting any text. Specs, decisions, ADO/DevOps comments, code review comments, meeting notes, status updates, Teams messages, emails, PR descriptions, or any document. Applies hard style rules and a self-check before presenting.
proofread
ethersphere
Check text against Swarm voice and style guidelines, flag violations, and optionally apply fixes
write
get-convex
Writing style guide for technical content, social media, blog posts, READMEs, git commits, and developer documentation. Optimized to avoid AI detection patterns. Use when writing any content beyond code.
documentation-review
stacklok
Reviews documentation for factual accuracy