agentleFS
yvesoryyvesory/academic-research-suite/skills/paper-self-review/SKILL.md

paper-self-review

Skill9 starsChanged 3 months agoNo licenceView on GitHub

Run a multi-perspective self-review of a paper draft before submission, rebuttal, or revision. Combines three complementary review modes: (1) a 5-persona editorial team simulation (Editor-in-Chief, three peer reviewers with field-specific expertise, and a Devil's Advocate) producing a referee-style report with editorial decision, (2) a methodology rigor audit covering experimental design, statistical soundness, claim-evidence alignment, threats to validity, and reproducibility, and (3) an adversarial kill-argument exercise where one fresh reviewer writes the strongest 200-word rejection memo and a second reviewer defends point-by-point to surface load-bearing weaknesses missed by balanced reviews. Use before submitting to a venue, before sending to advisor, or when preparing rebuttal material. Triggers: review my paper, peer review, self-review, referee report, critique paper, simulate review, rigor check, methodology audit, claim audit, kill argument, adversarial review, hostile review, reviewer-2 simulation, 自审, 模拟评审, 审查论文, 死论文.

4 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

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

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 8

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“Common” is measured: kept by at least 6 in 10 of the 3 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.

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.