← ClaudeAtlas

paper-reviewlisted

Simulate a full academic peer-review panel on a draft — examine a manuscript through five independent review lenses (significance, rigor & validity, evidence, argument, clarity), with the methodological criteria adapted to the paper type (CONSORT / STROBE / PRISMA / COREQ / Toulmin), a rebuttal round, a moderator, and a chief editor, then deliver a referee letter plus a scored verdict (Accept / Minor / Major Revision / Reject). Use this skill WHENEVER the user wants critical feedback on their own academic writing: "review my paper / essay / thesis chapter", "give me peer review on this draft", "is this ready to submit?", "what would a reviewer say about my manuscript", "critique my research proposal", or pastes a draft and asks how to improve it. Trigger even when the tool isn't named. Feedback is calibrated to the draft's stage (final / working / sketch / student) so a student essay isn't judged like a journal submission.
academicatstool-netizen/Cat_paper_review · ★ 0 · Code & Development · score 72
Install: claude install-skill academicatstool-netizen/Cat_paper_review
# Paper Review A six-phase simulated peer-review panel. It takes the author's **own draft** and returns a structured referee report plus a scorecard verdict — the kind of feedback a serious reviewer would give, calibrated to how finished the draft is. ``` intake (+type) ─▶ 5 lenses ─▶ rebuttal round ─▶ moderator ─▶ editor letter + scorecard ``` This is pure reasoning — no scripts. **You are one Claude playing all six roles in sequence within a single turn** — the "5 lenses" framing is conceptual, not a multi-agent runtime. The per-phase JSON is internal scratch; by default you deliver only the **review letter** and the **scorecard table**. The full pipeline, the five lenses, the **paper-type → standard mapping** (CONSORT, STROBE, PRISMA, COREQ, validity typology, Toulmin, NIH), the score/priority calibration, the draft-level tones, the verdict thresholds, the transparency & ethics flags, and every verbatim role prompt are in `references/review.md` — **load it before reviewing.** ## How to run it 1. **Default = review immediately. Don't gate behind a confirmation menu.** Once you have the draft, just review it — infer the **draft stage** from the message (any signal word → that stage; otherwise default to `working`), default to all five lenses and the user's language. **Don't ask the user to confirm things they already said.** Append ONE line after the verdict so they can correct the one thing that matters: *"I reviewed this as a **working draft** — if