G2
brycewang-stanford/Auto-Empirical-Research-Skills
Publication Specialist - Writing, Review, Pre-registration & Quality Assurance Light VS applied: Avoids template-based writing + audience-specific message design Absorbed G3 (Peer Review…
Structured peer review of manuscripts and grants. An agent skill from jaechang-hits/SciAgent-Skills.
$ npx skills add jaechang-hits/SciAgent-Skills --skill peer-review-methodology -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jaechang-hits/SciAgent-Skills peer-review-methodology --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/jaechang-hits/SciAgent-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/scientific-writing/peer-review-methodology .claude/skills/peer-review-methodology && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "peer-review-methodology" agent skill from https://github.com/jaechang-hits/SciAgent-Skills/tree/main/skills/scientific-writing/peer-review-methodology into .claude/skills/peer-review-methodology/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "peer-review-methodology", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/jaechang-hits/SciAgent-Skills/tree/main/skills/scientific-writing/peer-review-methodologyType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add jaechang-hits/SciAgent-Skills --skill peer-review-methodology -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jaechang-hits/SciAgent-Skills peer-review-methodology --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jaechang-hits/SciAgent-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/scientific-writing/peer-review-methodology .agents/skills/peer-review-methodology && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "peer-review-methodology" agent skill from https://github.com/jaechang-hits/SciAgent-Skills/tree/main/skills/scientific-writing/peer-review-methodology into .agents/skills/peer-review-methodology/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "peer-review-methodology", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jaechang-hits/SciAgent-Skills --skill peer-review-methodology -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jaechang-hits/SciAgent-Skills peer-review-methodology --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jaechang-hits/SciAgent-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/scientific-writing/peer-review-methodology .cursor/skills/peer-review-methodology && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "peer-review-methodology" agent skill from https://github.com/jaechang-hits/SciAgent-Skills/tree/main/skills/scientific-writing/peer-review-methodology into .cursor/skills/peer-review-methodology/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "peer-review-methodology", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/jaechang-hits/SciAgent-Skills.git --path skills/scientific-writing/peer-review-methodology--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add jaechang-hits/SciAgent-Skills --skill peer-review-methodology -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jaechang-hits/SciAgent-Skills peer-review-methodology --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jaechang-hits/SciAgent-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/scientific-writing/peer-review-methodology .gemini/skills/peer-review-methodology && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "peer-review-methodology" agent skill from https://github.com/jaechang-hits/SciAgent-Skills/tree/main/skills/scientific-writing/peer-review-methodology into .gemini/skills/peer-review-methodology/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "peer-review-methodology", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install jaechang-hits/SciAgent-Skills peer-review-methodologyInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add jaechang-hits/SciAgent-Skills --skill peer-review-methodology -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jaechang-hits/SciAgent-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/scientific-writing/peer-review-methodology .github/skills/peer-review-methodology && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "peer-review-methodology" agent skill from https://github.com/jaechang-hits/SciAgent-Skills/tree/main/skills/scientific-writing/peer-review-methodology into .github/skills/peer-review-methodology/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "peer-review-methodology", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jaechang-hits/SciAgent-Skills --skill peer-review-methodology -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jaechang-hits/SciAgent-Skills peer-review-methodology --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jaechang-hits/SciAgent-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/scientific-writing/peer-review-methodology .opencode/skills/peer-review-methodology && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "peer-review-methodology" agent skill from https://github.com/jaechang-hits/SciAgent-Skills/tree/main/skills/scientific-writing/peer-review-methodology into .opencode/skills/peer-review-methodology/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "peer-review-methodology", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
peer-review-methodologyStructured peer review of manuscripts and grants. An agent skill from jaechang-hits/SciAgent-Skills.
Peer Review Methodology is an agent skill from jaechang-hits/SciAgent-Skills. Structured peer review of manuscripts and grants. 7-stage evaluation: initial assessment, section review, statistical rigor, reproducibility, figure integrity, ethics, writing. Covers CONSORT/STROBE/PRISMA and report structure. For evidence quality see scientific-critical-thinking; scoring see scholar-evaluation.
Its SKILL.md is about 2.9k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Research & Science, covering Peer review, Reproducible research and ORMs and data access. It works with Prisma. The repository describes itself as: 197 bioinformatics & life science skills for Claude Code and AI agents — BixBench 92.0% accuracy. RNA-seq, single-cell, drug discovery, proteomics, and more. Powers OmicsHorizon. The licence is CC-BY-4.0.
3 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 82c862c. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Links to these hosts (documentation or services it may open):
publicationethics.orgequator-network.orgauthorservices.wiley.comFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Peer Review Methodology loads about 2.9k tokens when it runs. Until then it costs about 85 tokens; SKILL.md has 1,270 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from jaechang-hits/SciAgent-Skills at commit 82c862c, republished under its CC-BY-4.0 licence (© jaechang-hits). 1,270 words, ~2,907 tokens.
.claude/skills/peer-review-methodology/SKILL.md (or your agent's skills folder).Peer review is a systematic process for evaluating scientific manuscripts and grant proposals. This knowhow covers the complete review cycle: from initial assessment through detailed section-by-section evaluation, statistical rigor checks, reproducibility assessment, figure integrity verification, ethical considerations, and writing quality — culminating in a structured review report with actionable feedback.
| Review Type | Scope | Typical Length | Key Focus |
|---|---|---|---|
| Original research | Full evaluation | 1–3 pages | Rigor, novelty, reproducibility |
| Review/Meta-analysis | Coverage and bias | 1–2 pages | Completeness, search strategy, systematic approach |
| Methods paper | Validation | 1–2 pages | Comparison to existing methods, reproducibility |
| Short communication | Proportional | 0.5–1 page | Core findings rigor despite brevity |
| Grant proposal | Feasibility + significance | 1–3 pages | Innovation, approach, team, budget justification |
| Standard | Applies to | Key Check |
|---|---|---|
| CONSORT | Randomized controlled trials | Flow diagram, randomization, blinding, ITT analysis |
| STROBE | Observational studies | Study design, setting, participants, variables, bias |
| PRISMA | Systematic reviews / meta-analyses | Search strategy, PICO, risk of bias, forest plots |
| ARRIVE | Animal research | Species, sample size, randomization, 3Rs |
| MIAME | Microarray experiments | Platform, normalization, data deposit (GEO/ArrayExpress) |
| MINSEQE | Sequencing experiments | Read counts, mapping, QC metrics, data deposit (SRA) |
What are you reviewing?
├── Scientific manuscript
│ ├── Original research → Full 7-stage workflow
│ ├── Review / meta-analysis → Emphasize Stage 2 (Introduction + Methods) + Stage 4
│ ├── Methods paper → Emphasize Stage 3 (rigor) + Stage 4 (reproducibility)
│ └── Short communication → Abbreviated workflow (Stages 1, 2, 3, 7)
├── Grant proposal
│ └── Focus on: significance, innovation, approach feasibility, team qualifications
└── Not a document review
└── Use scientific-critical-thinking for evidence evaluation| Reviewer Situation | Focus Areas | Time Budget |
|---|---|---|
| First-round journal review | All 7 stages, full detail | 4–8 hours |
| Revision re-review | Only check if previous concerns addressed | 1–2 hours |
| Internal lab feedback | Stages 1–3, 7 (skip ethics, reporting standards) | 2–4 hours |
| Conference abstract | Stage 1 only + brief methods check | 30 min |
| Grant review | Significance + innovation + approach + team | 3–6 hours |
Read the whole manuscript once before writing any comments: Resist the urge to annotate during first reading. Your initial impression informs the summary statement and helps distinguish major from minor issues.
Separate description from judgment: For each concern, first state what you observed ("The authors report p=0.04 without correction for 12 comparisons"), then state why it's problematic ("This inflates the false positive rate"), then suggest a fix ("Apply Bonferroni or FDR correction and re-evaluate significance").
Number every comment for easy reference: Both major and minor comments should be sequentially numbered so authors can address each one explicitly in their response letter.
State your confidence level on statistical concerns: If you are uncertain about a statistical issue, say so explicitly ("I am not certain whether the normality assumption holds here — the authors should verify with a Shapiro-Wilk test or use a non-parametric alternative").
Check reporting standards compliance: Before writing the review, identify which reporting standard applies (CONSORT, STROBE, PRISMA, etc.) and use its checklist to verify completeness. Missing checklist items are legitimate major comments.
Acknowledge strengths explicitly: Every review should include 2–3 specific strengths. This is not politeness — it tells editors which aspects are sound and helps authors understand what NOT to change during revision.
Never request experiments beyond the study's scope: A reviewer should point out limitations, not redesign the study. "This limitation should be acknowledged in the Discussion" is appropriate. "The authors should run a new cohort with 500 patients" is not.
Be concrete about figure quality: Instead of "figures need improvement," say "Figure 3A: y-axis label missing units; error bars are not defined in the legend (SD vs SEM?); color coding is not colorblind-accessible."
Maintain anonymity and professionalism: In single/double-blind review, avoid self-referential comments ("In our previous work..."). Never use dismissive or condescending language. Frame all criticism constructively.
Match recommendation to evidence: If your comments are all minor, don't recommend rejection. If you have unresolvable major concerns about study design, don't recommend minor revision. The recommendation must be consistent with the severity of identified issues.
Reviewing what the paper should be instead of what it is: Judging the paper against your preferred experimental approach rather than evaluating whether the authors' approach is valid. How to avoid: Focus on whether the methods answer the stated research question, not on whether you would have used different methods.
Conflating statistical significance with scientific importance: A paper with p=0.001 can be trivial; a paper with p=0.06 can be groundbreaking. How to avoid: Evaluate effect sizes and practical significance separately from p-values. Ask "Does this matter?" not just "Is this significant?"
Scope creep in revision requests: Requesting additional experiments that constitute a new study rather than validation of the current one. How to avoid: Before writing a revision request, ask "Is this necessary to support the paper's current conclusions?" If it addresses a new question, suggest it as future work instead.
Overlooking positive controls: Checking for negative controls while ignoring whether the experiment demonstrates it CAN detect the claimed effect. How to avoid: For every experiment, check both "What would happen if the effect doesn't exist?" (negative control) AND "What demonstrates the assay actually works?" (positive control).
Copy-paste reviewing: Using the same boilerplate concerns across different manuscripts without engaging with the specific content. How to avoid: Every comment should reference a specific section, figure, or claim in THIS manuscript. Generic advice ("improve writing quality") is unhelpful.
Ignoring supplementary materials: Many critical methods details and validation data are in supplements. How to avoid: Always read supplementary materials, especially methods and figures referenced from the main text.
Asymmetric skepticism: Being more critical of findings that contradict your expectations while accepting confirmatory findings uncritically. How to avoid: Apply the same methodological scrutiny to all results regardless of whether you agree with the conclusions.
Initial assessment (read full manuscript without annotation): Identify central question, main findings, overall soundness, venue appropriateness. Write 2-3 sentence summary capturing the manuscript's essence
Section-by-section review: Evaluate each section (Abstract, Introduction, Methods, Results, Discussion, References) against specific criteria:
Statistical and methodological rigor: Check statistical assumptions, effect sizes, multiple testing correction, sample size justification, appropriate test selection, control adequacy, randomization, blinding
Reproducibility and transparency: Verify data availability (repositories, accession numbers), code availability, reporting standards compliance (CONSORT/STROBE/PRISMA/ARRIVE), protocol detail
Figure and data integrity: Check resolution, labeling, error bar definitions, color accessibility, signs of image manipulation, scale bars, data type appropriateness
Ethical considerations: Verify IRB/IACUC approval, informed consent, 3Rs compliance, conflicts of interest disclosure, funding disclosure, data privacy
Writing quality: Assess organization, language clarity, jargon use, narrative flow, accessibility to broad audience
After completing all stages, organize feedback into:
© jaechang-hits, CC-BY-4.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in skills/scientific-writing/peer-review-methodology of jaechang-hits/SciAgent-Skills.
Open the folder on GitHubat commit 82c862c
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in jaechang-hits/SciAgent-Skills, which our catalogue first saw on October 7, 2026.
Peer Review Methodology next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Peer Review Methodology this skilljaechang-hits/SciAgent-Skills | 374 | 1 repos | ~2.9k | Automated safety check: Pass | CC-BY-4.0 | |
| G2brycewang-stanford/Auto-Empirical-Research-Skills | 4.6k | — | ~4.5k | Automated safety check: Pass | Custom licence | |
| Method Writingaipoch/medical-research-skills | 1.9k | — | ~3.4k | Automated safety check: Pass | MIT | |
| Revedres Tables Figuresbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.5k | Automated safety check: Pass | MIT | |
| Revedres Transparency And Reproducibilitybrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Peer ReviewK-Dense-AI/claude-scientific-writer | 2.4k | 2 repos | ~3.1k | Automated safety check: Notes | MIT |
brycewang-stanford/Auto-Empirical-Research-Skills
Publication Specialist - Writing, Review, Pre-registration & Quality Assurance Light VS applied: Avoids template-based writing + audience-specific message design Absorbed G3 (Peer Review…
aipoch/medical-research-skills
Write and revise the Methods section of research papers to ensure reproducibility; use when preparing an IMRAD manuscript or responding to journal/reporting-guideline requirements (e.g…
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when designing the PRISMA flow diagram, forest/funnel plots, and coding/evidence tables for a Review of Educational Research (RER) review or meta-analysis.
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when settling coding reliability, open materials, PRISMA/MARS reporting, and a reproducible meta-analysis for a Review of Educational Research (RER) manuscript.
K-Dense-AI/claude-scientific-writer
Prepare evidence-bounded, constructive peer-review drafts and structured manuscript assessments.
neflibata-feng/MyArxiv-Agent
Core skill for the deep research and writing tool. An agent skill from neflibata-feng/MyArxiv-Agent.
jaechang-hits/SciAgent-Skills
NEB-IRC activation energy pipeline for reaction barriers using GFN2-xTB and pysisyphus.
jaechang-hits/SciAgent-Skills
3Dmol.js WebGL molecular visualization emitted as self-contained HTML.
jaechang-hits/SciAgent-Skills
Constraint-based (COBRA) analysis of genome-scale metabolic models: FBA, FVA, knockouts, flux sampling, production envelopes, gapfilling, media optimization.
jaechang-hits/SciAgent-Skills
Read, write, and edit ChemDraw CDX/CDXML files with RDKit's rdkit.Chem.rdChemDraw plus direct XML editing, always paired with a rendered PNG.
jaechang-hits/SciAgent-Skills
Programmatic PubMed access via NCBI E-utilities REST API. An agent skill from jaechang-hits/SciAgent-Skills.
jaechang-hits/SciAgent-Skills
Scaffold a new SciAgent-Skills entry. An agent skill from jaechang-hits/SciAgent-Skills.
Works with
Categories
Structured peer review of manuscripts and grants. An agent skill from jaechang-hits/SciAgent-Skills. Peer Review Methodology is an agent skill from jaechang-hits/SciAgent-Skills. Structured peer review of manuscripts and grants.
Peer Review Methodology fits situations like: tasks that involve Peer review; tasks that involve Reproducible research; tasks that involve ORMs and data access.
Run `npx skills add jaechang-hits/SciAgent-Skills --skill peer-review-methodology -a claude-code`. Or copy the skill folder (skills/scientific-writing/peer-review-methodology in jaechang-hits/SciAgent-Skills) into .claude/skills/peer-review-methodology in your project. Claude Code loads it when a task matches its description.
Run `npx skills add jaechang-hits/SciAgent-Skills --skill peer-review-methodology -a codex`. Or copy the skill folder (skills/scientific-writing/peer-review-methodology in jaechang-hits/SciAgent-Skills) into .agents/skills/peer-review-methodology in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jaechang-hits/SciAgent-Skills --skill peer-review-methodology -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/peer-review-methodology, .gemini/skills/peer-review-methodology, .github/skills/peer-review-methodology and .opencode/skills/peer-review-methodology in your project.
SKILL.md names no scripts, command-line tools or credentials: Peer Review Methodology is instructions for the agent only.
SKILL.md names 3 domains. As links in the text: publicationethics.org, equator-network.org and authorservices.wiley.com. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Peer Review Methodology is published under the CC-BY-4.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
About 2.9k tokens (SKILL.md is roughly 12k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Peer Review Methodology: G2 (brycewang-stanford/Auto-Empirical-Research-Skills, 4.6k stars), Method Writing (aipoch/medical-research-skills, 1.9k stars), Revedres Tables Figures (brycewang-stanford/Awesome-Journal-Skills, 1.2k stars) and Revedres Transparency And Reproducibility (brycewang-stanford/Awesome-Journal-Skills, 1.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
jaechang-hits (a GitHub user) maintains it in jaechang-hits/SciAgent-Skills, which has 374 GitHub stars. The repository holds 169 skills in this directory. The repository was last updated on September 29, 2026.
Source: jaechang-hits/SciAgent-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.