review
Skill0 starsChanged 15 days agoMITView on GitHub
Review one section of a scientific paper against the course-derived model for that section and report what is missing, weak or inconsistent, without rewriting it unasked. Sections are abstract, introduction, results-discussion, conclusions, title, cover-letter and response-to-reviewers. Name the section as the argument. Use when asked to review, critique, check, audit, proofread or give feedback on an abstract, introduction, results and discussion, conclusions, title, cover letter, or response to reviewers.
192 other projects use a version of this.
Adopted by
Most recently taken up by
- dzhng/skillstheir own version, first seen Nov 15, 2026
- muxy-app/muxytheir own version, first seen Nov 15, 2026
- macro-inc/macrotheir own version, first seen Nov 15, 2026
- yagizdo/quivertheir own version, first seen Nov 15, 2026
- markmhendrickson/neotomatheir own version, first seen Nov 15, 2026
- felipeam86/pipe-skillstheir own version, first seen Nov 15, 2026
Used with
Projects with it also use close-spec, design-with-images and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
dzhngSkillclose-spec
When a spec under specs/<feature>/ is done shipping (a write-spec build, or any planned task that produced a spec), archive it to specs/done/ and rewrite it from a build-plan into a durable rationale — the why, the principles, the invariants — pointing back to the real code for the how. Use when implementation has landed and the plan no longer matches what shipped, or the user says a feature/spec is finished. Pairs with [write-spec](../write-spec/SKILL.md) (the plan this closes) and [review](../review/SKILL.md) (run before closing).
Also in 5 projects that use this
dzhngSkilldesign-with-images
Explore UI and visual design with image generation, then iterate the real implementation against the user-selected concept. Use when brainstorming visual directions, offering mockup variants, or implementing an approved generated design; do not stop at the mockups or the first code approximation.
Also in 5 projects that use this
LambenthanSkilldaily-arxiv
每日从 arXiv 拉取新论文,过滤相关性,auto-ingest 高优先级论文,检测 SOTA 更新
Also in 5 projects that use this
LambenthanSkillexp-eval
实验判决门:Review LLM 独立评判实验结果 → 4 种判决路径 → 自动更新 claims confidence、ideas status、graph edges
Also in 5 projects that use this
- +3 more from dzhng
- +5 more from Lambenthan
Other versions192 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 192
- garrytan/gstack★ 142ksame name
- ansible/ansible★ 71ksame name
- docling-project/docling★ 71ksame name
- traefik/traefik★ 66ksame name
- ClickHouse/ClickHouse★ 51ksame name
- temporalio/temporal★ 24ksame name
- ccch1mneyyy/dsh-Go★ 24ksame name
- tisfeng/Easydict★ 15ksame name
- juicedata/juicefs★ 15ksame name
- elie222/inbox-zero★ 13ksame name
182 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.
0
Common
Most of the 156 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 59
If it does not exist, stop and say so, and point at /write <section>.
- Distinctive: line 64
Read the chosen reference in full and follow it.
- Very specific: line 73
Re-score the section if an evaluation exists: If paper-out/evaluation.md exists, follow "Re-scoring one section" in the evaluate skill's …
“Common” is measured: kept by at least 6 in 10 of the 156 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.
Files
/review
One entry point for critiquing every section of a paper. The researcher says what to review; this skill
loads the checks for that section and runs them. Each section is judged against its own model, so the
checks live in references/.
Usage
/review abstract
/review introduction src/introduction.tex
/review response-to-reviewers
/review # infers the section, else asksSections
| Section | Reference |
| Abstract | abstract |
| Introduction | introduction |
| Results and discussion | results-discussion |
| Conclusions | conclusions |
| Title | title |
| Cover letter | cover-letter |
| Response to reviewers | response-to-reviewers |
Methods is not offered, because the course gives no model to judge it against. Say so if asked.
Before anything else
- Check for
paper-out/STATE.mdand read it, withdecisions.mdand the relevantinterviews/*.md, so you do not re-ask what is already settled and can check the section against earlier decisions. - Load the style rules. Invoke
paper-writing-styleand read itsreferences/human-voice.md. The project's ownCLAUDE.mdoutranks them. If it is not installed, say so, and fall back to the condensed rules at the bottom of the/writeskill'sreferences/<section>.mdif that skill is installed. - Lock the language. Language of the user's first message, whole run. Rewrites are English.
Pick the section
- From the argument. Match it loosely:
resultsanddiscussionare one section;conclusion,rebuttal,reviewer response,cover,letterall map to a row above. - From a file path, if given: the file's name or contents say which section it is.
- From context, if there is no argument: the open file, or the section
paper-out/STATE.mdsays was last written. Say what you inferred and let the researcher correct it. - Otherwise ask. Offer the most likely sections (at most four, plus "other"), or list all seven in chat. Never guess a section and start reviewing.
Needs a draft
A review needs text to review. Find the section in src/ and main.tex, following the \input list.
If it does not exist, stop and say so, and point at /write <section>. Do not review an outline or
invent a draft to criticise.
Run it
Read the chosen reference in full and follow it. Do not mix checks from two sections.
After it finishes
- Update
paper-out/before you finish, asreferences/session-state.mdinpaper-writing-stylesets out, creating it if absent: this section's row inSTATE.md(reviewed on this date, how many findings), adecisions.mdentry for what was accepted or declined and why,open-questions.mdfor what was left, and the section's score inevaluation.mdif it was re-scored. Name the files you wrote. A run is not finished until this is done. - Re-score the section if an evaluation exists. If
paper-out/evaluation.mdexists, follow "Re-scoring one section" in theevaluateskill'sreferences/rubric.md: score the section again against the storedpaper-out/venue-criteria.md, replace that section's block, recompute the overall score, and show the change (Introduction 6.0 to 7.0, overall 6.4 to 6.7). The user does not paste the venue text again. If there is noevaluation.md, do nothing and do not create one. Ifvenue-criteria.mdis missing or unreadable, or theevaluateskill is not installed, skip the re-score and say why. - Offer to apply the fixes with
/write <section>, which picks up the suggestions in its Update mode.
Hard rules
- Never rewrite the researcher's text unasked. Report, then offer rewrites for the weak parts only.
- Never invent a result, number or citation key in a suggested rewrite. Flag it with
\todo{}or% TODO:. - Never review a section that does not exist.
- Never create
evaluation.mdorvenue-criteria.md, and never score from criteria you did not read from the file. Only/evaluatestarts an evaluation. - Never finish a run without updating
paper-out/. Say which files you changed. - Never emit an em dash (
---).
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
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.

