Skip to content
Skills Library
Science & research · Review & audit

proofread-math

/proofread-math

Conservatively proofread mathematical prose and LaTeX for grammar, typography, syntax, notation consistency, cross-references, and uniquely forced local mathematical typos. Use for explicit math-proofreading requests and final self-review of theorem-, proof-, or equation-heavy edits. Not for correctness audits, referee reports, or source verification.

Repository
mathbox ↗
Licence
MIT
Last repository change
02.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
5
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 02.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Conservatively proofread mathematical prose and LaTeX for grammar, typography, syntax, notation consistency, cross-references, and uniquely forced local mathematical typos. Use for explicit math-proofreading requests and final self-review of theorem-, proof-, or equation-heavy edits. Not for correctness audits, referee reports, or source verification.

Original author description

Conservatively proofread mathematical prose and LaTeX for grammar, typography, syntax, notation consistency, cross-references, and uniquely forced local mathematical typos. Use for explicit math-proofreading requests and final self-review of theorem-, proof-, or equation-heavy edits. Not for correctness audits, referee reports, or source verification.

How it works

  1. Select the mode
  2. Workflow
  3. Mathematical-token policy
  4. Reviewer notes
  5. Output
Original SKILL.md headings · 88 lines, 492 words
SKILL.md preview
---
name: proofread-math
description: >-
  Conservatively proofread mathematical prose and LaTeX for grammar, typography, syntax, notation consistency, cross-references, and uniquely forced local mathematical typos. Use for explicit math-proofreading requests and final self-review of theorem-, proof-, or equation-heavy edits. Not for correctness audits, referee reports, or source verification.
---

# Conservative mathematical proofreading

Proofread; do not invent, replace, shorten or substantively repair proofs. Preserve the mathematics, notation, macros,
authorial voice, language variant, and project conventions.

## Select the mode

- **Edit mode:** the caller explicitly asks to correct a file or pasted text.
- **Review-only mode:** the caller asks for findings, comments, or a check
  without edits.
- **Self-review mode:** invoked after a broader edit; inspect only the changed
  hunks and enough context to resolve notation, references, and prose. Correct
  routine issues only inside changed hunks; report issues elsewhere.

When corrections are not explicitly requested, default to review-only mode. For pasted LaTeX in edit mode,
return corrected LaTeX. For repository files, do not rewrite unrelated text.
If coverage is partial, state the exact scope reviewed.

## Workflow

1. Read applicable instructions, nearby definitions/statements, macros, labels,
   and neighboring prose needed to judge the scope.
2. Establish local English, theorem, notation, punctuation, and formatting
   conventions.
3. Review prose and display integration.
4. Review LaTeX structure, environments, delimiters, labels, references,
   citations, and custom commands.
5. Review local mathematical consistency without auditing correctness, which
   belongs to `proof-audit`.
6. Apply only minimal, high-confidence edits; do not normalize equivalent LaTeX
   or replace correct wording by preference.
7. Re-read every changed sentence/display in context.
8. Run documented, proportionate validation when available; never invent a
   build or install dependencies.

Citation syntax is proofreading; substantive source questions use available
`literature-check` (`mathbox:literature-check` in plugin installations), or return
the exact source obligation if unavailable.

The detailed checklist is in [checklist.md](references/checklist.md).

## Mathematical-token policy

A change to an operator, relation, sign, coefficient, variable, index, exponent,
subscript, superscript, quantifier, hypothesis, conclusion, domain, codomain, or
proof step is a **mathematical-token change**.

Make one only when the intended correction is uniquely forced by immediate
context, isolated and typographical, and does not require a new argument or
alter downstream reasoning. List every such change explicitly.

Otherwise leave the source unchanged and report the issue. A repeated pattern
alone does not justify changing a sign or index. An unbound symbol may signal a
missing definition. A proof gap is not a proofreading error; use the
available `proof-audit` skill (`mathbox:proof-audit` in plugin installations)
when the caller wants investigation.

## Reviewer notes

Report unresolved issues outside the manuscript by default. Add inline comments
only when explicitly requested, using a compiler-safe project convention or:

```latex
% REVIEWER NOTE: [precise issue and what must be verified]
```

Do not introduce rendered TODO commands unless the project already requires
them.

## Output

For edited repository files, report:

```text
Proofread: [file or scope]
- Routine edits: [categories or none]
- Mathematical-token changes: [location and exact change or none]
- Unresolved issues: [location and issue or none]
- Validation: [command/result or not run with reason]
- Coverage: [only when partial]
```

For pasted text, return corrected source first, then the same categories. For
review-only mode, order findings by mathematical/meaning-changing risk, LaTeX
errors, then language/typography. If no objective issue remains, say so and make
no change.
Files in this package (5)
  • SKILL.md 4 KB
  • agents/openai.yaml 1 KB
  • evals/evals.json 3 KB
  • evals/trigger-evals.json 2 KB
  • references/checklist.md 1 KB

Versions

The database has no other skills named proofread-math.

Database snapshot: 13.11.2026 · package version 0ed611ca1090 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100proofread
    Proofreads a finished text for typos, grammar, punctuation, consistency, and formatting, fixing only errors, listing every fix, and flagging style questions. Use when someone asks to "proofread", "check my grammar", "spell check", "check for typos", "catch mistakes", "give it a…
  • 100proofread
    Proofread and conservatively copy-edit prose, files, or translations with optional Harper linting and protected-span checks. Use for grammar, clarity, polish, or translation review.
  • 100referee
    Referee a whole mathematical manuscript for correctness, edge cases, notation, exposition and claim calibration. Use for a referee report, whole-paper stress test, or section-by-section manuscript audit. Do not use for a focused claim or proof audit, proofreading alone, a…
  • 100proofreading
    Proofread and correct text for grammar, spelling, punctuation, style, clarity, and consistency, with support for multiple style guides and readability analysis. Use when the user requests proofreading or provides relevant inputs for this workflow.
  • 90proofread
    Proofread papers and manuscripts. Checks grammar, typos, layout, consistency, writing quality. Produces report without editing files. Use when finding surface-level errors, not substantive academic critique.
  • 100theorem-proving
    Construct and verify mathematical proofs using LaTeX typesetting and computational verification via jupyter_execute. Use when the user asks to prove a theorem, verify a mathematical argument, construct a formal proof, or check proof correctness computationally.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.