skills/43-wentorai-research-plugins/skills/research/paper-review/paper-critique-framework/SKILL.md
Structured framework for writing peer review reports and paper critiques
npx skillsauth add brycewang-stanford/Awesome-Agent-Skills-for-Empirical-Research paper-critique-frameworkInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Writing constructive peer reviews is a core academic skill. This framework provides a systematic approach to evaluating manuscripts — from initial read-through to the final referee report. It covers what reviewers should assess, how to structure feedback, and how to calibrate between different review outcomes (accept, revise, reject). Applicable to conference papers, journal articles, and internal lab reviews.
Read only these elements:
After Pass 1, answer:
□ What is the main claim?
□ What type of contribution? (empirical, theoretical, system, survey)
□ Is it within the venue's scope?
□ Does the abstract accurately represent the content?
□ Initial impression: novel or incremental?
Read the full paper. Annotate as you go:
Annotation symbols:
? = I don't understand this
! = This is interesting / strong point
X = I disagree / see a problem
→ = This needs more evidence or justification
≈ = This is similar to [existing work] — check novelty
Focus on:
For papers you're seriously evaluating:
## Summary (3-5 sentences)
[Describe what the paper does, the approach, and the main finding.
Demonstrate that you understood the paper.]
## Strengths (bulleted list)
- S1: [Specific strength with evidence from the paper]
- S2: [Another strength]
- S3: [Another strength]
## Weaknesses (bulleted list, ordered by severity)
- W1 (Major): [Specific weakness + why it matters + suggestion to fix]
- W2 (Major): [Another major weakness]
- W3 (Minor): [A less critical issue]
- W4 (Minor): [Another minor issue]
## Questions for Authors
- Q1: [Something you'd like clarified]
- Q2: [A concern that the authors might be able to address]
## Detailed Comments
[Page/line-specific comments, typos, suggestions]
## Overall Assessment
Recommendation: [Strong Accept / Accept / Weak Accept / Borderline /
Weak Reject / Reject / Strong Reject]
Confidence: [High / Medium / Low]
| Dimension | Questions to Ask | Weight | |-----------|-----------------|--------| | Novelty | Is the idea new? Is the contribution beyond incremental? | High | | Significance | Would this matter to the community? Does it advance the field? | High | | Soundness | Are the methods correct? Are conclusions supported? | High | | Clarity | Is it well-written? Can it be understood and reproduced? | Medium | | Completeness | Are related works covered? Are experiments thorough? | Medium | | Reproducibility | Could someone replicate this? Code/data available? | Medium |
Strong Accept: Significant contribution, technically sound, well-written.
Would be a highlight of the venue.
Accept: Solid contribution with minor issues. Advances the field.
Worth publishing as-is or with minor revisions.
Weak Accept: Has merit but notable weaknesses. Contribution is real but modest.
Borderline for this venue; would be accepted at a less selective venue.
Borderline: Equal arguments for and against. Significant weaknesses offset
by some novelty. Depends on other reviews.
Weak Reject: Interesting direction but fundamental issues not addressed.
Major revisions needed that likely require a new submission cycle.
Reject: Significant problems in novelty, soundness, or relevance.
Not suitable for this venue even with revisions.
Strong Reject: Fundamental flaws. Clearly below threshold.
| Pitfall | Better Approach | |---------|----------------| | "The writing needs improvement" (vague) | Give 2-3 specific examples with suggested fixes | | Rejecting for not solving YOUR problem | Evaluate the paper on its own stated goals | | Demanding impossible experiments | Suggest feasible improvements within scope | | Ignoring supplementary material | Check appendix — authors may have addressed your concern | | Being harsh without being constructive | Every weakness should include a suggestion for improvement | | Reviewing too quickly | Block dedicated time; a rushed review harms both authors and science | | Citing only your own work as "missing" | Only cite if genuinely relevant, not self-promotion |
During review, check:
□ Are human subjects involved? Was IRB/ethics approval obtained?
□ Are there potential harms from the technology described?
□ Is the data collection ethical? (Consent, privacy, bias)
□ Are dual-use concerns addressed? (Misuse potential)
□ Are limitations and societal implications discussed?
development
Conduct rigorous thematic analysis (TA) of qualitative data following Braun and Clarke's (2006) six-phase framework. Use whenever the user mentions 'thematic analysis', 'TA', 'Braun and Clarke', 'qualitative coding', 'identifying themes', or asks for help analysing interviews, focus groups, open-ended survey responses, or transcripts to identify patterns. Also trigger for questions about inductive vs theoretical coding, semantic vs latent themes, essentialist vs constructionist epistemology, building a thematic map, or writing up a qualitative findings section. Covers all six phases, the four upfront analytic decisions, the 15-point quality checklist, and the five common pitfalls. Produces a Word document write-up and an annotated thematic map. Does NOT cover IPA, grounded theory, discourse analysis, conversation analysis, or narrative analysis — use a different method for those.
development
Guide users through writing a systematic literature review (SLR) following the PRISMA 2020 framework. Use this skill whenever the user mentions 'systematic review', 'systematic literature review', 'SLR', 'PRISMA', 'PRISMA 2020', 'PRISMA flow diagram', 'PRISMA checklist', or asks for help writing, structuring, or auditing a literature review that follows reporting guidelines. Also trigger when the user asks about inclusion/exclusion criteria for a review, search strategies for databases like Scopus/WoS/PubMed, study selection processes, risk of bias assessment, or narrative synthesis for a review paper. This skill covers the full PRISMA 2020 checklist (27 items), produces a Word document manuscript in strict journal article format, generates an annotated PRISMA flow diagram, and enforces APA 7th Edition referencing throughout. It does NOT cover meta-analysis or statistical pooling. By Chuah Kee Man.
testing
Performs placebo-in-time sensitivity analysis with hierarchical null model and optional Bayesian assurance. Use when checking model robustness, verifying lack of pre-intervention effects, or estimating study power.
data-ai
Fit, summarize, plot, and interpret a chosen CausalPy experiment. Use after the causal method has been selected, including when configuring PyMC/sklearn models and scale-aware custom priors.