agentleFS
texra-aitexra-ai/texra-scientific-skills/skills/manuscript-review/SKILL.md

manuscript-review

Skill4 starsChanged 7 months agoMITView on GitHub

Audit technical manuscripts for mathematical correctness, logical soundness, notation consistency, evidence quality, and figure or code alignment. Use when Codex needs to review a paper, verify derivations, prioritize findings, or produce a rigorous findings-first assessment instead of rewriting prose blindly.

5 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

9 rules. 0 are common, 9 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 9

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill for serious review passes on papers, notes, appendices, or technical drafts where the main job is to find problems, verify …

    line 10
  2. Distinctive:

    Read the full manuscript context first, including appendices, bibliography, macros, figures, and any supporting code that drives results.

    line 14
  3. Distinctive:

    Verify critical calculations independently when feasible.

    line 16
  4. Distinctive:

    Use computational verification tools when available for symbolic algebra, identities, spot checks, and code-backed results.

    line 17
  5. Distinctive:

    Check code-manuscript consistency when the paper depends on scripts, notebooks, generated figures, or implemented algorithms.

    line 19
  6. Distinctive:

    Check whether the manuscript actually delivers the goals stated in the abstract and introduction.

    line 20
  7. Distinctive:

    Check appendices before claiming a derivation is missing.

    line 26
  8. Distinctive:

    Prefer a short list of high-signal findings over a noisy dump of minor edits.

    line 29
  9. Distinctive:

    If no major issues are found, say that explicitly and note any residual uncertainty or untested areas.

    line 30

“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “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

Manuscript Review

When to use this skill

Use this skill for serious review passes on papers, notes, appendices, or technical drafts where the main job is to find problems, verify important claims, and report actionable findings.

Workflow

  1. Read the full manuscript context first, including appendices, bibliography, macros, figures, and any supporting code that drives results.
  2. Identify the main claims and the highest-risk derivations, proofs, experiments, and references before going broad.
  3. Verify critical calculations independently when feasible. Check limiting cases, dimensions, signs, factors, boundary conditions, and whether stated results follow from the setup.
  4. Use computational verification tools when available for symbolic algebra, identities, spot checks, and code-backed results. If you verify something numerically or symbolically, say so explicitly in the findings.
  5. Trace notation across the document. Confirm symbols are defined before use and stay stable across sections, figures, and code.
  6. Check code-manuscript consistency when the paper depends on scripts, notebooks, generated figures, or implemented algorithms.
  7. Check whether the manuscript actually delivers the goals stated in the abstract and introduction.
  8. Produce findings first. Order them by severity and point to exact locations.
  9. Distinguish confirmed errors, likely issues, and open questions. Do not blur them together.

Quality Bar

  • Check appendices before claiming a derivation is missing.
  • Focus on issues that affect validity, interpretation, reproducibility, or reader comprehension.
  • Be specific about what you verified and how.
  • Prefer a short list of high-signal findings over a noisy dump of minor edits.
  • If no major issues are found, say that explicitly and note any residual uncertainty or untested areas.

For a formal audit pass, use references/review-checklist.md when the manuscript is mathematically dense, has code-backed figures or computations, or needs a full findings report.

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.