agentleFS
texra-aitexra-ai/texra-scientific-skills/skills/inline-paper-critic/SKILL.md

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.

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
  1. Distinctive:

    Use this skill for inline technical review of mathematical or derivation-heavy papers when the output should be comments embedded in the …

    line 10
  2. Distinctive:

    Read the entire manuscript, including appendices and auxiliary files, before deciding that a step is missing or unjustified.

    line 14
  3. Distinctive:

    If a derivation is already handled in an appendix, say so and adjust severity accordingly rather than treating the main text as simply …

    line 17
  4. Very specific:

    When the document already uses a \criticize{comment}{severity}{confidence}-style macro, preserve that format.

    line 18
  5. Distinctive:

    If the macro is missing, provide a minimal command definition before inserting annotations:

    line 19
  6. Distinctive:

    Keep the document's existing color/theme conventions when present.

    line 25
  7. Distinctive:

    Use inline comments strategically.

    line 27
  8. Distinctive:

    When a calculation checks out, leave explicit verification comments when that helps the author distinguish true problems from confirmed …

    line 28
  9. Distinctive:

    Ensure every inline comment is valid LaTeX and can remain in the document without breaking compilation.

    line 29
  10. Distinctive:

    Check appendices before accusing the paper of omission.

    line 33
  11. Distinctive:

    Use severity and confidence consistently.

    line 35
  12. Distinctive:

    Treat severity as impact on validity and confidence as certainty of the diagnosis, not as two versions of the same number.

    line 36
  13. Distinctive:

    If you verified something as correct, say what you checked.

    line 38

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

  1. Read the entire manuscript, including appendices and auxiliary files, before deciding that a step is missing or unjustified.
  2. Expand important derivations mentally or on scratch paper before commenting. A good inline critique should come from actual verification, not surface-level suspicion.
  3. Prioritize issues that affect validity: broken proofs, missing essential steps, unjustified coefficients, hidden assumptions, incorrect limits, or inconsistent claims.
  4. If a derivation is already handled in an appendix, say so and adjust severity accordingly rather than treating the main text as simply wrong.
  5. 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.
  6. 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.

  7. Use inline comments strategically. Group related minor issues and reserve the harshest comments for problems that really threaten the result.
  8. When a calculation checks out, leave explicit verification comments when that helps the author distinguish true problems from confirmed material.
  9. 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.