원클릭으로
peer-review
You must use this when critiquing academic manuscripts, evaluating methodological rigor, or providing structured reviewer feedback.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
You must use this when critiquing academic manuscripts, evaluating methodological rigor, or providing structured reviewer feedback.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
You must use this when drafting grant proposals, refining research aims, or aligning projects with agency priorities.
You must use this when synthesizing existing knowledge, identifying research gaps, or tracing the evolution of scientific ideas.
You must use this when conducting PRISMA-standard systematic reviews, protocol development, or Risk of Bias assessment.
You must use this when producing any research prose — literature reviews, syntheses, analyses, methodology descriptions, discussion sections, abstracts, or any written output intended for an academic audience.
You must use this when investigating complex claims across diverse sources or fact-checking contradictory information.
Use this when starting a new research project or managing a complex, multi-step research workflow.
| name | peer-review |
| description | You must use this when critiquing academic manuscripts, evaluating methodological rigor, or providing structured reviewer feedback. |
| tools | ["WebSearch","WebFetch","Bash","Read","Grep","Glob"] |
<source_resolution>
Verify references and survey the field through the database backends owned by the literature-review skill, not web search alone: uv run <literature-review-dir>/scripts/openalex_cli.py (resolve DOIs/titles, citation counts, related work), europepmc_api.py (life-science full text and citation graphs), search_arxiv.py (preprints), read_paper.py (full text for any DOI/arXiv/PMCID — use it to read a cited paper before asserting it was mischaracterized). Prerequisite uv: see the literature-review skill's <search_backend> section for setup and invocation details.
</source_resolution>
<output_format>
Recommendation: [Accept/Minor Rev/Major Rev/Reject]
Executive Summary: [2-3 sentences on core contribution and primary concern]
Dimensional Scores (1-5):
Detailed Comments:
Final Verdict Justification: [Detailed PhD-level reasoning for the recommendation] </output_format>
After the review, ask: - Should I check for specific "Seminal Works" that might have been missed? - Would you like me to refine the "Response to Reviewers" strategy? - Should I analyze the manuscript's fit for a specific target journal (e.g., CVPR, Nature, NEJM)?