peer-review
Skill1 starsChanged 3 months agoApache-2.0View on GitHub
Prepare evidence-bounded, constructive peer-review drafts and structured manuscript assessments. Use for authorized review of scientific manuscripts, protocols, preprints, or research proposals; reporting-guideline selection; claim–evidence checks; methods, statistics, reproducibility, ethics, figure/table, and citation critique; or revision-response planning.
- Reads credentials
51 other projects use a version of this, 5 of them edited.
Adopted by
Most recently taken up by
- KPISTOLAS/claude-skillsedited, first seen Nov 16, 2026
- Ivan-propio/claude-skillstheir own version, first seen Nov 16, 2026
- lengrufeng2008/dsh-skill-librarytheir own version, first seen Nov 15, 2026
- patricksavalle/investigate-journalism-skillstheir own version, first seen Nov 15, 2026
- BrightGold70/skillstheir own version, first seen Nov 8, 2026
- QSOLKCB/CLAUDE-SKILLS-AGItheir own version, first seen Nov 8, 2026
Used with
Projects with it also use usfiscaldata, research-grants and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
yf8578Skillusfiscaldata
Query the U.S. Treasury Fiscal Data API for federal financial data including national debt, government spending, revenue, interest rates, exchange rates, and savings bonds. Access 54 datasets and 182 data tables with no API key required. Use when working with U.S. federal fiscal data, national debt tracking (Debt to the Penny), Daily Treasury Statements, Monthly Treasury Statements, Treasury securities auctions, interest rates on Treasury securities, foreign exchange rates, savings bonds, or any U.S. government financial statistics.
Also in 7 projects that use this
garri333Skillresearch-grants
Write competitive research proposals for NSF, NIH, DOE, DARPA, and Taiwan NSTC. Agency-specific formatting, review criteria, budget preparation, broader impacts, significance statements, innovation narratives, and compliance with submission requirements.
Also in 11 projects that use this
garri333Skillresearch-lookup
Look up current research information using Perplexity's Sonar Pro Search or Sonar Reasoning Pro models through OpenRouter. Automatically selects the best model based on query complexity. Search academic papers, recent studies, technical documentation, and general research information with citations.
Also in 13 projects that use this
SoljournerSkillget-available-resources
Enumerate installed packages, databases, and tools for engineering workflows
Also in 10 projects that use this
- +8 more from garri333
Other versions51 projects use a version of this.
Word for word · 1
- zh123012/claude-skills★ 1100% same
Edited · 5
- K-Dense-AI/claude-scientific-writer★ 2.6k90% same
- PracticalSwan/agent-skills★ 2263% same
- Luooops/skills★ 190% same
- KPISTOLAS/claude-skills★ 078% same
- patoangolano/bio-stack★ 078% same
Wrote their own version · 45
- Norman-bury/research-writing-skill★ 3.4ksame name
- Norman-bury/articlewriting-skill★ 3.4ksame name
- wu-yc/LabClaw★ 1.1ksame name
- LeonChaoX/qinyan-academic-skills★ 910same name
- poemswe/co-researcher★ 139same name
- qinyan-ai/qinyan-academic-skills★ 80same name
- Barrios88/barrios-skills★ 63same name
- richard-kim-79/archora-skills★ 49same name
- a-lottes/aSPARK★ 25same name
- EtherealMingo/university-teacher-skills★ 16same name
35 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository28 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- academic-paper-reviewSkill
- citation-managementSkill
- decision-makingSkill
- experimental-designSkill
- hypothesis-generationSkill
- paper-lookupSkill
- peer-reviewSkill
- read-arxiv-paperSkill
- scientific-critical-thinkingSkill
- scientific-writingSkill
- statistical-analysisSkill
- statistical-powerSkill
- systematic-literature-reviewSkill
- venue-templatesSkill
- academic-paper-reviewSkill
- citation-managementSkill
- experimental-designSkill
- hypothesis-generationSkill
- paper-lookupSkill
- read-arxiv-paperSkill
- scientific-critical-thinkingSkill
- scientific-writingSkill
- statistical-analysisSkill
- statistical-powerSkill
- systematic-literature-reviewSkill
- venue-templatesSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
26 rules. 0 are common, 19 are distinctive, and 7 are very specific to this project.
0
Common
Most of the 41 edited versions we read keep these.
19
Distinctive
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 17
Before reading or analyzing unpublished content:
- Distinctive: line 20
Check the target venue’s review, confidentiality, co-review, retention, and AI/tool policies.
- Distinctive: line 22
Default to local-only processing.
- Distinctive: line 24
If authorization is unclear, do not inspect or quote the manuscript.
- Very specific: line 31
Read broad environment state, .env files, API keys, or credentials
- Distinctive: line 32
Call a network, LLM, or image API from bundled tools
- Distinctive: line 38
Delete local copies and derivatives when policy requires.
- Very specific: line 40
Read references/ethical_review_practice.md before handling confidential material.
- Distinctive: line 46
Read the complete authorized submission and relevant supplements
- Distinctive: line 47
Verify every factual statement, calculation, citation, and manuscript location
- Distinctive: line 90
Do not infer absent content.
- Distinctive: line 94
Create a short neutral map:
- Distinctive: line 104
Do not write an acceptance/rejection recommendation.
- Very specific: line 122
Use the current base guideline, explanation/elaboration, applicable extensions, and target venue policy.
- Very specific: line 144
Start from assets/claim_evidence_matrix_template.csv.
- Very specific: line 160
Use references/common_issues.md and references/statistical_reproducibility.md.
- Very specific: line 169
Start from assets/statistical_reproducibility_template.json.
- Distinctive: line 182
Do not claim reproduction unless authorized inputs were actually run with documented commands, environment, and outputs.
- Distinctive: line 186
Check applicable approvals, consent, welfare, privacy, community governance, funding, sponsor role, conflicts, authorship/contribution, …
- Very specific: line 207
Start from assets/citation_references_template.csv.
- Distinctive: line 219
Every major/minor comment should include:
- Distinctive: line 244
Do not place ordinary criticism only in confidential notes.
- Distinctive: line 256
Verify all locations and evidence.
- Distinctive: line 257
Remove unsupported or speculative criticism.
- Distinctive: line 262
Ensure no invented citation, experiment, reanalysis, or outcome.
- Distinctive: line 263
Follow the documented deletion/retention rule.
“Common” is measured: kept by at least 6 in 10 of the 41 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Peer Review
Support an accountable human reviewer with a rigorous, fair, actionable assessment. Treat every unpublished submission and review as confidential.
Mandatory safety boundary
Before reading or analyzing unpublished content:
- Confirm the user is authorized by the publisher, editor, author, or other material owner.
- Check the target venue’s review, confidentiality, co-review, retention, and AI/tool policies.
- Record conflicts, competence limits, requested scope, and specialist-review needs.
- Default to local-only processing.
If authorization is unclear, do not inspect or quote the manuscript. Ask for confirmation or use only the bundled local CLIs, whose reports do not echo manuscript text.
Never:
- Send unpublished manuscript, supplement, review, or editorial text to an external service without specific publisher/author authorization and venue permission
- Upload confidential content to a public model, search engine, citation service, grammar tool, plagiarism checker, or image service
- Reuse content for training, benchmarking, product improvement, or unrelated research
- Read broad environment state,
.envfiles, API keys, or credentials - Call a network, LLM, or image API from bundled tools
- Invoke another skill or a PDF/image pipeline automatically
- Impersonate an assigned reviewer, editor, journal, funder, or author
- Fabricate manuscript details, review findings, citations, analyses, experiments, reproduction, or an editorial outcome
- Announce a decision that belongs to an editor or panel
Delete local copies and derivatives when policy requires; otherwise retain only what the controlling policy authorizes. Record deletion or retention without copying confidential content into the record.
Read references/ethical_review_practice.md before handling confidential material.
Human accountability
Label generated text as a working draft. The accountable human must:
- Read the complete authorized submission and relevant supplements
- Verify every factual statement, calculation, citation, and manuscript location
- Resolve conflicts and disclose assistance as required
- Rewrite comments in their own expert judgment
- Submit through the authorized channel
Automated coverage, consistency, or lint results are not peer review and do not establish manuscript merit.
Intake gate
Copy and complete assets/review_intake_template.json, then run:
python3 scripts/validate_review_intake.py completed-intake.jsonProceed only when status is READY_FOR_LOCAL_REVIEW.
The validator blocks:
- Undocumented authorization
- Missing human accountability
- Unassessed or unresolved conflicts
- Unknown review model or unchecked venue policy
- Unauthorized AI assistance
- External service use
- Data reuse
- Missing deletion/retention planning
It validates declarations, not their truth.
Review workflow
1. Establish scope and available evidence
Record:
- Submission type and stage
- Review question and requested focus
- Target venue and review model
- Materials actually available: manuscript, supplements, protocol, registration, analysis plan, data/code statement, prior decision, or response letter
- Competence areas and limits
- Missing material that prevents assessment
Do not infer absent content. Use “not reported” or “not available for review.”
2. Orient without deciding
Create a short neutral map:
- Research question
- Population or system
- Design and unit
- Intervention, exposure, test, or model
- Comparator/reference
- Outcomes and timing
- Principal claims
Do not write an acceptance/rejection recommendation. Identify what evidence would be needed to evaluate each claim.
3. Select reporting guidance
Copy assets/study_profile_template.json and run:
python3 scripts/select_reporting_guidelines.py local-profile.jsonFor checklist coverage:
python3 scripts/select_reporting_guidelines.py \
local-profile.json \
--coverage local-coverage.csvUse the current base guideline, explanation/elaboration, applicable extensions, and target venue policy. See references/reporting_standards.md.
Critical distinction: reporting completeness is not design quality, risk of bias, validity, or merit. Never convert missing items into an automatic score or publication judgment.
4. Map claims to evidence
Prioritize central, causal, mechanistic, safety, diagnostic, prediction, and generalization claims.
For each claim, record:
- Location and claim ID
- Supporting result, figure, table, analysis, or citation IDs
- Direction, magnitude, population, outcome, timepoint, and uncertainty alignment
- Limitation or alternative explanation
- Bounded requested action
Run:
python3 scripts/validate_claim_evidence.py local-claim-matrix.csvStart from assets/claim_evidence_matrix_template.csv. The report emits IDs and counts, not claim text.
5. Review methods and statistics
Assess in this order:
- Question and target quantity
- Design and unit of inference
- Sampling, allocation, controls, masking, and timing
- Sample-size or precision rationale
- Inclusion, exclusion, attrition, and missingness
- Analysis–design alignment and assumptions
- Multiplicity and prespecification
- Effect estimates, uncertainty, denominators, and harms
- Interpretation, causality, and generalizability
Use references/common_issues.md and references/statistical_reproducibility.md.
For a structured local audit:
python3 scripts/audit_statistics_reproducibility.py \
local-statistics-reproducibility.jsonStart from assets/statistical_reproducibility_template.json. Request specialist review when a central method exceeds competence; do not hide uncertainty behind a generic critique.
6. Review reproducibility and transparency
Check, as applicable:
- Protocol, registration, amendments, and analysis-plan consistency
- Data provenance, exclusions, transformations, and accession IDs
- Software, package, model, and parameter versions
- Code, environment, seeds, run instructions, and tests
- Data, code, materials, and model availability or justified restrictions
- Domain metadata standards
Do not claim reproduction unless authorized inputs were actually run with documented commands, environment, and outputs.
7. Review ethics and integrity
Check applicable approvals, consent, welfare, privacy, community governance, funding, sponsor role, conflicts, authorship/contribution, registration, biosafety, and dual-use concerns.
Describe observable evidence and uncertainty. Do not accuse authors or investigate them. Route credible concerns through the confidential editor channel under venue policy.
8. Review figures, tables, and citations
For figures and tables, assess:
- Consistency with text and supplements
- Denominators, units, axes, scales, uncertainty, and legends
- Accessible encoding and sufficient context
- Image acquisition/processing disclosure and source-data policy
This skill has no image-generation or PDF-conversion workflow. Use only user-authorized local artifacts and tools.
For Pandoc-style citations such as [@ref-id]:
python3 scripts/audit_citations.py local-manuscript.md local-references.csvStart from assets/citation_references_template.csv. This checks key consistency and identifier format only; it does not verify that a source exists or supports a claim.
9. Draft actionable comments
Generate a private scaffold only after intake passes:
python3 scripts/generate_review_scaffold.py \
completed-intake.json \
-o private-review.mdEvery major/minor comment should include:
- Location
- Observation
- Evidence or criterion
- Why it matters
- Requested action
Prioritize:
- Claim–evidence alignment
- Methods and statistical validity
- Reproducibility and transparency
- Ethics and participant/animal protection
- Reporting needed for appraisal
- Figures, tables, limitations, and citations
Requests for new work must be necessary to support a central claim and proportionate to scope. Offer narrowing, clarification, sensitivity analysis, correction, or limitation language when that is sufficient.
10. Keep channels separate
Comments to authors contain the scientific review, strengths, major/minor comments, and limitations.
Confidential comments to editor contain only policy-appropriate conflicts, competence limits, assistance disclosure, specialist requests, or substantiated integrity/process concerns that require a separate route.
Do not place ordinary criticism only in confidential notes. Do not reveal reviewer identity under an anonymized process.
11. Lint and finalize
python3 scripts/lint_review.py private-review.mdThe linter checks channel separation, unresolved placeholders, a narrow abusive-language lexicon, role/decision phrases, and required actionability fields. It emits line numbers and rule IDs, not review text. Human tone and scientific review remain mandatory.
Before handoff:
- Verify all locations and evidence.
- Remove unsupported or speculative criticism.
- Confirm professional, non-abusive language.
- State review limits and specialist needs.
- Disclose permitted assistance.
- Remove all placeholders.
- Ensure no invented citation, experiment, reanalysis, or outcome.
- Follow the documented deletion/retention rule.
Local tool index
scripts/validate_review_intake.py— scope, authorization, conflicts, policy, handlingscripts/select_reporting_guidelines.py— dated selector and non-scoring coverage auditscripts/validate_claim_evidence.py— claim/evidence alignment matrixscripts/audit_statistics_reproducibility.py— methods/statistics/reproducibility checklistscripts/audit_citations.py— local citation/reference consistencyscripts/generate_review_scaffold.py— separated private Markdown scaffoldscripts/lint_review.py— tone, channel, and actionability lint
Full schemas and exit codes: references/tool_reference.md.
References and assets
references/ethical_review_practice.md— COPE/ICMJE duties, confidentiality, AI, channelsreferences/reporting_standards.md— current major guidelines and verified domain standardsreferences/statistical_reproducibility.md— methods, statistics, and reproducibility reviewreferences/common_issues.md— contextual issue patterns and constructive responsesreferences/security_validation.md— baseline remediation and local scan resultsassets/source_ledger.csv— authoritative sources verified 2026-07-23assets/reporting_guidelines.json— local selector catalogassets/review_scaffold_template.md— private structured draft
The source ledger is dated. Recheck live primary sources and the target venue policy for a later review, without exposing confidential manuscript text in search queries.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

