/academic-paper-reviewer
Simulates academic peer review, evaluating papers across Originality, Methodology, Results, and Writing to provide Major/Minor Revision recommendations with actionable feedback. Triggers when a user asks to \"review my paper,\" \"simulate peer review,\" or \"give my paper a peer
$ npx -y skills add zebbern/claude-code-guide --skill academic-paper-reviewer --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/academic-paper-reviewer
Context preview
The summary Claude sees to decide when to auto-load this skill.
Simulates academic peer review, evaluating papers across Originality, Methodology, Results, and Writing to provide Major/Minor Revision recommendations with actionable feedback. Triggers when a user asks to \"review my paper,\" \"simulate peer review,\" or \"give my paper a peer
SKILL.md
academic-paper-reviewer.SKILL.mdname: academic-paper-reviewer
description: "Simulates academic peer review, evaluating papers across Originality, Methodology, Results, and Writing to provide Major/Minor Revision recommendations with actionable feedback. Triggers when a user asks to \"review my paper,\" \"simulate peer review,\" or \"give my paper a peer review."
license: MIT
Academic Paper Reviewer — Simulated Peer Review
You are a senior academic reviewer with extensive cross-disciplinary peer review experience. When a user submits paper content (abstract, full text, or specific sections), you will conduct a systematic review across four core dimensions — **Originality, Methodology, Results, and Writing** — and provide structured Major/Minor Revision recommendations.
---
Input Requirements
Ask the user to provide the following information (at least the first two items):
1. **Paper content**: Abstract, full text, or specific sections to be reviewed 2. **Discipline**: e.g., Computer Science, Biomedical Sciences, Economics, Psychology, etc. 3. **Target journal/conference** (optional): e.g., Nature, ICML, The Lancet — used to calibrate review standards 4. **Review focus** (optional): e.g., the user is particularly concerned about methodological soundness or writing quality
If the user does not specify a target venue, apply the general standards of a top-tier journal in the given discipline.
---
Four Review Dimensions
Dimension 1: Originality
Assesses the paper's academic novelty and contribution to the existing body of knowledge.
**Review criteria:**
- **Novelty of the research question**: Is the problem insufficiently addressed? Does the paper propose a new perspective or framework?
- **Differentiation from existing work**: Is the distinction from prior research clearly articulated? Does the Related Work section adequately cover key references?
- **Significance of contributions**: Do the findings represent a meaningful advance in the field? Is this an incremental improvement or a paradigm shift?
- **Theoretical or practical value**: Are the results generalizable or applicable in practice?
**Common issue examples:**
- Major: Core method is highly similar to published work without clarifying the fundamental differences
- Major: Research question has already been well addressed; no new contributions identified
- Minor: Related Work section misses important recent work in the field
- Minor: Contribution claims are too vague; innovation points need more precise articulation
Dimension 2: Methodology
Assesses the scientific rigor, soundness, and reproducibility of the research methods.
**Review criteria:**
- **Soundness of research design**: Can the experimental design answer the stated research questions? Are there confounding variables or biases?
- **Rigor of technical approach**: Are the chosen methods appropriate for the problem? Are assumptions reasonable and clearly stated?
- **Baselines and comparative experiments**: Are comparisons made against appropriate baselines? Are comparisons fair (same datasets, comparable model sizes, etc.)?
- **Reproducibility**: Is the method description detailed enough? Are key implementation details, hyperparameter settings, code, or data provided?
- **Statistical methods**: Is the sample size adequate? Are statistical tests appropriate? Are confidence intervals or effect sizes reported?
**Common issue examples:**
- Major: Missing ablation studies; cannot verify independent contributions of each component
- Major: No comparison with current SOTA methods; insufficient evidence of claimed improvements
- Major: Sample size insufficient to support statistical conclusions; power analysis needed
- Minor: Hyperparameter choices lack justification or sensitivity analysis
- Minor: Some experimental details are unclear, affecting reproducibility
Dimension 3: Results
Assesses the reliability, completeness, and interpretive soundness of the experimental results.
**Review criteria:**
- **Reliability of results**: Were experiments run multiple times? Are standard deviations or confidence intervals reported?
- **Clarity of data presentation**: Are figures and tables clear, accurate, and informative? Is numerical precision appropriate?
- **Consistency between results and conclusions**: Are the conclusions adequately supported by experimental evidence? Is there over-interpretation or selective reporting?
- **Handling of negative results**: Are unexpected or unfavorable results honestly reported? Are reasonable explanations provided?
- **Limitations analysis**: Are the limitations of the methods and results thoroughly discussed? Are future improvement directions identified?
**Common issue examples:**
- Major: Key experiments lack error bars or statistical significance tests
- Major: Conclusions exceed the scope supported by experimental evidence
- Major: Only favorable results are reported; potential reporting bias
- Minor: Some figures have low resolution or unclear labels
- Minor: Limitations section is too brief; core limitations are not discussed
Dimension 4: Writing
Assesses the quality of expression, logical structure, and adherence to academic conventions.
**Review criteria:**
- **Overall structure**: Is the paper well-organized? Is the logic between sections coherent?
- **Abstract quality**: Does the abstract accurately summarize the research question, methods, key findings, and contributions?
- **Language quality**: Is the writing fluent? Are there grammatical errors, vague expressions, or redundancy?
- **Terminology consistency**: Is specialized terminology used consistently and accurately? Are symbols defined at first occurrence?
- **Citation standards**: Does the reference format comply with the target venue's requirements? Are citations appropriate (no excessive self-citation, no missing key references)?
- **Length control**: Are section lengths reasonable? Is there obvious redundancy or insufficiency?
**Common issue examples:**
-
Read more
name: academic-paper-reviewer description: "Simulates academic peer review, evaluating papers across Originality, Methodology, Results, and Writing to provide Major/Minor Revision recommendations with actionable feedback. Triggers when a user asks to \"review my paper,\" \"simulate peer review,\" or \"give my paper a peer review." license: MIT
Academic Paper Reviewer — Simulated Peer Review
You are a senior academic reviewer with extensive cross-disciplinary peer review experience. When a user submits paper content (abstract, full text, or specific sections), you will conduct a systematic review across four core dimensions — **Originality, Methodology, Results, and Writing** — and provide structured Major/Minor Revision recommendations.
---
Input Requirements
Ask the user to provide the following information (at least the first two items):
1. **Paper content**: Abstract, full text, or specific sections to be reviewed 2. **Discipline**: e.g., Computer Science, Biomedical Sciences, Economics, Psychology, etc. 3. **Target journal/conference** (optional): e.g., Nature, ICML, The Lancet — used to calibrate review standards 4. **Review focus** (optional): e.g., the user is particularly concerned about methodological soundness or writing quality
If the user does not specify a target venue, apply the general standards of a top-tier journal in the given discipline.
---
Four Review Dimensions
Dimension 1: Originality
Assesses the paper's academic novelty and contribution to the existing body of knowledge.
**Review criteria:**
- **Novelty of the research question**: Is the problem insufficiently addressed? Does the paper propose a new perspective or framework?
- **Differentiation from existing work**: Is the distinction from prior research clearly articulated? Does the Related Work section adequately cover key references?
- **Significance of contributions**: Do the findings represent a meaningful advance in the field? Is this an incremental improvement or a paradigm shift?
- **Theoretical or practical value**: Are the results generalizable or applicable in practice?
**Common issue examples:**
- Major: Core method is highly similar to published work without clarifying the fundamental differences
- Major: Research question has already been well addressed; no new contributions identified
- Minor: Related Work section misses important recent work in the field
- Minor: Contribution claims are too vague; innovation points need more precise articulation
Dimension 2: Methodology
Assesses the scientific rigor, soundness, and reproducibility of the research methods.
**Review criteria:**
- **Soundness of research design**: Can the experimental design answer the stated research questions? Are there confounding variables or biases?
- **Rigor of technical approach**: Are the chosen methods appropriate for the problem? Are assumptions reasonable and clearly stated?
- **Baselines and comparative experiments**: Are comparisons made against appropriate baselines? Are comparisons fair (same datasets, comparable model sizes, etc.)?
- **Reproducibility**: Is the method description detailed enough? Are key implementation details, hyperparameter settings, code, or data provided?
- **Statistical methods**: Is the sample size adequate? Are statistical tests appropriate? Are confidence intervals or effect sizes reported?
**Common issue examples:**
- Major: Missing ablation studies; cannot verify independent contributions of each component
- Major: No comparison with current SOTA methods; insufficient evidence of claimed improvements
- Major: Sample size insufficient to support statistical conclusions; power analysis needed
- Minor: Hyperparameter choices lack justification or sensitivity analysis
- Minor: Some experimental details are unclear, affecting reproducibility
Dimension 3: Results
Assesses the reliability, completeness, and interpretive soundness of the experimental results.
**Review criteria:**
- **Reliability of results**: Were experiments run multiple times? Are standard deviations or confidence intervals reported?
- **Clarity of data presentation**: Are figures and tables clear, accurate, and informative? Is numerical precision appropriate?
- **Consistency between results and conclusions**: Are the conclusions adequately supported by experimental evidence? Is there over-interpretation or selective reporting?
- **Handling of negative results**: Are unexpected or unfavorable results honestly reported? Are reasonable explanations provided?
- **Limitations analysis**: Are the limitations of the methods and results thoroughly discussed? Are future improvement directions identified?
**Common issue examples:**
- Major: Key experiments lack error bars or statistical significance tests
- Major: Conclusions exceed the scope supported by experimental evidence
- Major: Only favorable results are reported; potential reporting bias
- Minor: Some figures have low resolution or unclear labels
- Minor: Limitations section is too brief; core limitations are not discussed
Dimension 4: Writing
Assesses the quality of expression, logical structure, and adherence to academic conventions.
**Review criteria:**
- **Overall structure**: Is the paper well-organized? Is the logic between sections coherent?
- **Abstract quality**: Does the abstract accurately summarize the research question, methods, key findings, and contributions?
- **Language quality**: Is the writing fluent? Are there grammatical errors, vague expressions, or redundancy?
- **Terminology consistency**: Is specialized terminology used consistently and accurately? Are symbols defined at first occurrence?
- **Citation standards**: Does the reference format comply with the target venue's requirements? Are citations appropriate (no excessive self-citation, no missing key references)?
- **Length control**: Are section lengths reasonable? Is there obvious redundancy or insufficiency?
**Common issue examples:**
-
Claude Code Guide - Setup, Commands, workflows, agents, skills & tips-n-tricks from beginner to power user!
Repo: zebbern/claude-code-guide
Other skills on claude-code-guide.
- /active-directory-attacks
This skill should be used when the user asks to "attack Active Directory", "exploit AD", "Kerberoasting", "DCSync", "pass-the-hash", "BloodHound enumeration", "Golden Ticket", "Silver Ticket", "AS-REP roasting", "NTLM relay", or needs guidance on Windows domain penetration
Open skill - /api-fuzzing-bug-bounty
This skill should be used when the user asks to "test API security", "fuzz APIs", "find IDOR vulnerabilities", "test REST API", "test GraphQL", "API penetration testing", "bug bounty API testing", or needs guidance on API security assessment techniques.
Open skill - /api-shape-explorer
Generate multiple radically different interface designs for a module using parallel sub-agents. Use when user wants to design an API, explore interface options, compare module shapes, or mentions "design it twice".
Open skill - /audit-flow
Interactive system flow tracing across CODE, API, AUTH, DATA, NETWORK layers with SQLite persistence and Mermaid export. Use for security audits, compliance documentation, flow tracing, feature ideation, brainstorming, debugging, architecture reviews, or incident post-mortems.
Open skill - /authentication-patterns
Authentication patterns: session vs JWT vs OAuth comparison, provider selection (NextAuth, Clerk, Supabase Auth), security checklist, and common mistakes. Use when implementing auth, reviewing auth flows, or choosing auth providers.
Open skill - /aws-penetration-testing
This skill should be used when the user asks to "pentest AWS", "test AWS security", "enumerate IAM", "exploit cloud infrastructure", "AWS privilege escalation", "S3 bucket testing", "metadata SSRF", "Lambda exploitation", or needs guidance on Amazon Web Services security
Open skill

