inline-paper-critic
Skill4 starsChanged 7 months agoMITView on GitHub
Critically annotate technical papers with inline comments about mathematical gaps, unjustified steps, risky assumptions, and verified results. Use when Codex needs to leave compile-safe review comments directly in a LaTeX manuscript, especially in a `\\criticize{comment}{severity}{confidence}` style for derivation-heavy papers where appendices and hidden calculations must be checked carefully.
In this repository8 other files it gives its agents.
- literature-searchSkill
- manuscript-reviewSkill
- mathematical-enhancerSkill
- math-ocrSkill
- scientific-presenterSkill
- scientific-simplifierSkill
- tikz-figure-builderSkill
- writing-commenterSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. About 0 are common, 12 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈12
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Use this skill for inline technical review of mathematical or derivation-heavy papers when the output should be comments embedded in the …
- Distinctive: line 14
Read the entire manuscript, including appendices and auxiliary files, before deciding that a step is missing or unjustified.
- Distinctive: line 17
If a derivation is already handled in an appendix, say so and adjust severity accordingly rather than treating the main text as simply …
- Very specific: line 18
When the document already uses a \criticize{comment}{severity}{confidence}-style macro, preserve that format.
- Distinctive: line 19
If the macro is missing, provide a minimal command definition before inserting annotations:
- Distinctive: line 25
Keep the document's existing color/theme conventions when present.
- Distinctive: line 27
Use inline comments strategically.
- Distinctive: line 28
When a calculation checks out, leave explicit verification comments when that helps the author distinguish true problems from confirmed …
- Distinctive: line 29
Ensure every inline comment is valid LaTeX and can remain in the document without breaking compilation.
- Distinctive: line 33
Check appendices before accusing the paper of omission.
- Distinctive: line 35
Use severity and confidence consistently.
- Distinctive: line 36
Treat severity as impact on validity and confidence as certainty of the diagnosis, not as two versions of the same number.
- Distinctive: line 38
If you verified something as correct, say what you checked.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Inline Paper Critic
When to use this skill
Use this skill for inline technical review of mathematical or derivation-heavy papers when the output should be comments embedded in the manuscript rather than a separate review memo.
Workflow
- Read the entire manuscript, including appendices and auxiliary files, before deciding that a step is missing or unjustified.
- Expand important derivations mentally or on scratch paper before commenting. A good inline critique should come from actual verification, not surface-level suspicion.
- Prioritize issues that affect validity: broken proofs, missing essential steps, unjustified coefficients, hidden assumptions, incorrect limits, or inconsistent claims.
- If a derivation is already handled in an appendix, say so and adjust severity accordingly rather than treating the main text as simply wrong.
- When the document already uses a
\criticize{comment}{severity}{confidence}-style macro, preserve that format. Otherwise adapt to the local inline annotation convention without losing the same discipline. If the macro is missing, provide a minimal command definition before inserting annotations:
\newcommand{\criticize}[3]{\textcolor{red}{\textbf{[#2|#3]} #1}}Keep the document's existing color/theme conventions when present.
- Use inline comments strategically. Group related minor issues and reserve the harshest comments for problems that really threaten the result.
- When a calculation checks out, leave explicit verification comments when that helps the author distinguish true problems from confirmed material.
- Ensure every inline comment is valid LaTeX and can remain in the document without breaking compilation.
Quality Bar
- Check appendices before accusing the paper of omission.
- Base comments on actual mathematical verification whenever possible.
- Use severity and confidence consistently; do not inflate comments just to sound forceful.
- Treat severity as impact on validity and confidence as certainty of the diagnosis, not as two versions of the same number.
- A compile-safe inline review comment is better than a sharper comment that breaks the document.
- If you verified something as correct, say what you checked.
For a deeper pass over severity discipline, appendix-first review, and compile-safe comment writing, use references/critique-checklist.md.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

