agentleFS
JihaoXinJihaoXin/paper-machine/skills/reviewer-mindset/SKILL.md

reviewer-mindset

Skill0 starsChanged 3 months agoMITView on GitHub

Review a draft the way a hostile reviewer would, before submission. Use after a draft compiles, when asked to critique or improve a paper, or before delivering to the user. Produces specific, actionable objections rather than praise.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    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:

    1. Abstract and conclusion only: Do they claim the same thing?

    line 21
  2. Distinctive:

    Do not inflate minor issues to look thorough, and do not soften a blocking issue to make the draft look closer to done than it is.

    line 75

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Reviewer Mindset

The job

Find the objection that would sink this paper, while there is still time to answer it. Not to be discouraging. A reviewer will find it anyway, and finding it yourself is the only version where you get to respond.

Self-review by an agent fails in a predictable way: it produces generous, generic feedback ("the paper is well written, consider adding more experiments"). That is worse than no review, because it manufactures confidence. Review against evidence, not impression.

Read in this order

1. Abstract and conclusion only. Do they claim the same thing? Can you state the finding in one sentence with a number in it? If not, the paper does not yet know what it is arguing.

2. Every number. For each, ask: which file produced this? Is the precision honest? Is a comparison stated that was never computed? See numbers-traceable.

3. Every figure and table. Is it referenced in the text? Does the caption say what to conclude? Is it legible at print size? Does it plot what the text says it plots?

4. The bibliography. Sample five entries and look them up. If any does not exist, stop reviewing and fix the bibliography, because there are probably more. See citation-discipline.

5. Related work against the claim of novelty. Is there a paper that already does this? Search for it specifically, do not rely on the draft's own account.

6. The method, for reimplementability. Could you build this from the description alone? List what is missing.

Questions that find real problems

  • What result would have falsified the hypothesis? Was that outcome possible under this experimental design?
  • Is the baseline given the same tuning effort as the method?
  • Are the gains inside the variance? If variance is unreported, that is itself the finding.
  • Does the conclusion generalise beyond the conditions tested?
  • Is any experiment described in the plan missing from the results?
  • Would the headline claim survive if the weakest experiment were removed?

Write the review usefully

Each point gets a location, a problem, and a fix:

Section 4.2, Table 2: the 12% improvement is reported without variance.
  Three seeds are mentioned in 4.1 but only means appear.
  Fix: report standard deviation, or state that the difference is
  within noise.

Not: "the evaluation could be more rigorous."

Severity, honestly assigned

  • Blocking: invented citations, unsourced numbers, a claim the experiments do not support, a missing disclosure
  • Major: unfair baseline, missing variance, an uncited close competitor
  • Minor: prose, formatting, figure legibility

Do not inflate minor issues to look thorough, and do not soften a blocking issue to make the draft look closer to done than it is.

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.