paper-critique-framework
Structured framework for writing peer review reports and paper critiques
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Structured framework for writing peer review reports and paper critiques
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Route empirical-research requests through the Auto-Empirical Research Skills catalog when this whole repository is installed as one skill in Codex, CodeBuddy, Claude Code, or another IDE. Use to choose and load the right vendored AERS skill for causal inference, econometrics, replication, data acquisition, manuscript writing, peer review and referee responses, citation checking, de-AIGC editing, or full empirical-paper workflows without reading the entire repository at once.
公司金融实证研究的"漏斗式选题查找器"。互动开场先后询问 (1) 研究方向、(2) 候选标题数量 N, 再扫描全球文献(已出版英文学术期刊 + SSRN working paper + 全球高校 department seminar 1 年内日程),基于 Edmans (2024) "1000 Rejections" 红线生成 N 个候选标题,**通过并行 subagent(Agent 工具)批量生成计划书 + 查新;每个 subagent 必须强制调用 Skill 工具加载 econfin-proposal 与 novelty-check 两个预设 skill 完成各自模块**,**只有当 novelty score >= 9 时(即 JF/JFE/RFS 顶刊层次),subagent 才把 proposal + 查新报告合并的 md 写入 F:\Dropbox\CC\选题大全\<研究方向短名>\(以"简短选题名称-分数"命名,子文件夹名由 Step 0 从用户输入的研究方向派生);< 9 分的选题在 subagent 内部直接丢弃,绝不写盘、绝不输出**。当用户说"找选题"、"帮我找选题"、"想做 X 方向"、 "empirical CF idea search"、"批量生成研究计划书"、"100 ideas"、"econfin-idea-finder" 时触发。
Create and compile beautiful Beamer presentations following the Rhetoric of Decks philosophy. Use when making slides, creating decks, or compiling .tex presentation files.
Scaffold a new research project with standard directory structure, CLAUDE.md template, and documented README. Use this at the start of every new project to ensure consistent organization.
Download, split, and deeply read academic PDFs. Use when asked to read, review, or summarize an academic paper. Splits PDFs into 4-page chunks, reads them in small batches, and produces structured reading notes — avoiding context window crashes and shallow comprehension.
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
| name | paper-critique-framework |
| description | Structured framework for writing peer review reports and paper critiques |
| metadata | {"openclaw":{"emoji":"📋","category":"research","subcategory":"paper-review","keywords":["peer review","paper critique","referee report","academic review","manuscript evaluation","constructive feedback"],"source":"wentor-research-plugins"}} |
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?