Przejdź do treści
Biblioteka skilli
Nauka i badania · Przegląd i audyt

peer-review

/peer-review

Recenzuje rękopis, wniosek lub analizę jak staranny recenzent: sprawdza metody względem tez i statystykę względem projektu badania, oddziela problemy blokujące od uwag i daje rekomendację.

Repozytorium
openscience ↗
Licencja
Apache-2.0
Ostatnia zmiana repozytorium
25.10.2026

Ocena i bezpieczeństwo

100/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść35 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
11
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
1
Przestarzałość

Brak sygnałów. Repozytorium zmienione 25.10.2026, bez odwołań do wycofanych modeli i API.

Licencja

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

Co robi i kiedy

Recenzuje rękopis, wniosek lub analizę jak staranny recenzent: sprawdza metody względem tez i statystykę względem projektu badania, oddziela problemy blokujące od uwag i daje rekomendację.

Oryginalny opis (EN)

Reviews a manuscript, proposal, analysis or result the way a careful referee does, reading the whole artifact, checking the methods against the claims, the statistics against the design, the figures against the numbers, and reporting BLOCKING issues separately from observations, with a calibrated recommendation. Use for peer review, critical appraisal of a paper or claim, pre-submission review of the user's own draft, grant review, or evaluating research rigor. For fixing the text afterwards use paper-writing; for an independent second opinion delegate a read to an explore worker.

Jak działa

  1. Non-negotiables
  2. Workflow
  3. Report
  4. Before you hand it over
Sekcje z nagłówków SKILL.md, w oryginale · 93 linii, 741 słów
Podgląd SKILL.md
---
name: peer-review
description: Reviews a manuscript, proposal, analysis or result the way a careful referee does, reading the whole artifact, checking the methods against the claims, the statistics against the design, the figures against the numbers, and reporting BLOCKING issues separately from observations, with a calibrated recommendation. Use for peer review, critical appraisal of a paper or claim, pre-submission review of the user's own draft, grant review, or evaluating research rigor. For fixing the text afterwards use paper-writing; for an independent second opinion delegate a read to an explore worker.
summary: "Referee a manuscript, proposal or result: BLOCKING vs observations, calibrated verdict."
category: core
role: workflow
allowed-tools: [Read, glob, grep, Bash, python, literature, webfetch, task]
license: MIT
version: 1.0.0
author: Synthetic Sciences
metadata:
  upstream: K-Dense-AI/claude-scientific-writer
  upstream-url: https://github.com/K-Dense-AI/claude-scientific-writer
  upstream-license: MIT
  upstream-relationship: references and scripts derived
  adapted-by: Synthetic Sciences
  skill-author: Synthetic Sciences
  adapted-from: K-Dense peer-review and scientific-critical-thinking (MIT)
---

# Peer review

A review's job is to tell the authors, and the editor, whether the evidence supports the
claims, and what would have to change if it does not. It is not a summary, not a list of
typos, and not an opinion about how interesting the topic is. Read everything, check
what can be checked, and separate what blocks from what would help.

## Non-negotiables

1. **Read the whole artifact** including appendices, supplementary tables, and code when it
   is provided. A review of the first eight pages is not a review.
2. **Check, do not just read.** Recompute a number when the inputs are there; rerun a
   provided analysis; compare a figure to the table it summarizes; check that the test
   matches the design (paired vs unpaired, multiple comparisons, dependence).
3. **BLOCKING or OBSERVATION, for every point.** Blocking means the central claim is not
   supported as written: leakage, a wrong test, an unfair baseline, a result that does not
   appear in the data, a claim outside the study's scope. Observations improve the paper
   but do not change whether it is right.
4. **Locate every issue.** Section, page, table, figure, equation, line. "The statistics
   are weak" is not a finding; "Table 2 reports p < 0.05 from a t-test on 3 seeds per
   condition without correction across 12 comparisons" is.
5. **Calibrate.** The recommendation follows from the blocking list, not from taste.
   `references/calibration.md` and `references/scoring-rubric.md` define the scale.
6. **Constructive and specific.** Each blocking issue names the fix or the experiment that
   would resolve it. Tone stays neutral; the authors are colleagues.

## Workflow

- [ ] Read fully; write the paper's claims in your own words (three lines).
- [ ] For each claim: the evidence offered, and whether it supports the claim as worded.
- [ ] Methods and statistics check (`references/statistical-pitfalls.md`, `references/common-issues.md`).
- [ ] Figures, tables and reporting check (`references/paper-mechanics.md`, `references/reporting-standards.md`).
- [ ] Reproducibility and ethics check.
- [ ] Classify, calibrate, write the report.

**Claims.** State what the paper claims to have shown, with the scope it claims (which
data, which conditions). Everything else is checked against this.

**Evidence per claim.** For each claim: which table, figure or theorem carries it; whether
the comparison is fair (same data, budget, tuning); whether the effect size clears the
variance (seeds, confidence intervals, n); whether the metric measures the claim; whether
a simpler explanation fits the same evidence.

**Methods and statistics.** Design matched to the question; randomization and controls;
sample size and power; the test's assumptions met; corrections for multiple comparisons;
leakage between train and test or between selection and evaluation; hyperparameter tuning
on the test set; reported variance. `references/evidence-hierarchy.md` for study designs,
`references/common-biases.md` and `references/logical-fallacies.md` for reasoning faults.

**Figures and reporting.** Every figure's claim visible without the prose; axes, units,
uncertainty; numbers in text equal to numbers in tables; reporting checklist for the field
(CONSORT, PRISMA, ARRIVE, the venue's reproducibility checklist).

**Reproducibility.** Code and data availability; enough detail to rerun; seeds; compute.
If code is attached, run the smallest thing that tests a central number.

**An independent second read.** When the artifact is long, the stakes are high, or your
own draft is under review, delegate one read to an `explore` worker (Task tool,
`subagent_type: "explore"`) with the artifact paths, this skill's name to load, and the
specific angle: statistics, leakage, claims versus evidence. The worker is read-only; ask
it to report BLOCKING and OBSERVATION items. Merge its BLOCKING findings with yours; do not
average them away.

## Report

```markdown
## Summary
Three sentences: what the work claims, what it does, what the evidence shows.

## Blocking
1. [Section/Table] Issue. Why it undermines the claim. What would resolve it.

## Observations
- [Location] Suggestion.

## Recommendation
Accept / Minor revision / Major revision / Reject, with the one-sentence reason tied to the
blocking list. Confidence: high / medium / low, and why.
```

For the user's own draft, the same report, then the offer to fix the blocking items with
paper-writing. For grant review, `references/reviewer-expectations.md` covers criteria
and scoring conventions.

## Before you hand it over

- Every issue has a location and a fix.
- The recommendation follows from the blocking list; a paper with no blocking issues is not
  rejected for taste, and a paper with one is not accepted for polish.
- Numbers you recomputed are shown with your method.
- What you could not check is listed as unchecked, not assumed fine.
Pliki w paczce (11)
  • SKILL.md 6 KB
  • references/calibration.md 7 KB
  • references/common-biases.md 11 KB
  • references/common-issues.md 19 KB
  • references/evidence-hierarchy.md 13 KB
  • references/logical-fallacies.md 18 KB
  • references/paper-mechanics.md 10 KB
  • references/reporting-standards.md 10 KB
  • references/reviewer-expectations.md 16 KB
  • references/scoring-rubric.md 9 KB
  • references/statistical-pitfalls.md 16 KB

Wersje

RepozytoriumWynikLicencja
Ta strona · synthetic-sciences/openscience100Apache-2.0
alexandermattturner/agent-sanitizer100Apache-2.0
aipoch/medical-research-skills100MIT
sokolmarek/researcher100MIT
Prismer-AI/Prismer100MIT
foryourhealth111-pixel/Vibe-Skills95Apache-2.0
elias-ramzi/weblatexmcp95MIT
bestagentkits/agency-skills95MIT
Marazii/research-co-pilot91MIT

Migawka bazy z 28.10.2026 · wersja paczki b2b2f791ec9b (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 100paper-review
    Recenzuje manuskrypt jak recenzent naukowy: krytykuje metody i statystykę, daje uwagi do artykułu przed wysłaniem i ocenia zgłoszenie z pliku PDF.
  • 100paper-review
    Prowadzi wieloagentowy przegląd artykułu naukowego: krytykuje rękopis, znajduje słabe punkty, symuluje recenzję koleżeńską i pomaga przygotować pracę do złożenia.
  • 90academic-reviser
    Recenzuje szkice artykułów CS, AI i ML jak krytyczny recenzent w trzech rundach (dowody, argument, styl) ze statusem weryfikacji i śledzeniem długu dowodowego.
  • 100review-neuro
    Przeprowadza przedpublikacyjną recenzję rękopisu z neuronauki, jak recenzent naukowy, i zwraca uwagi do poprawy przed zgłoszeniem.
  • 90peer-review-manuscript
    Uruchamia wieloagentową recenzję naukową rękopisu w PDF, Markdown lub LaTeX i przygotowuje decyzję redakcyjną z uzasadnieniem.
  • 100review-paper
    Recenzuje pełny manuskrypt względem wskazanego czasopisma: równoległe agenty oceniają styl, spójność, niepoparte tezy, matematykę, wykresy i wkład, z podziałem CRITICAL, MAJOR i MINOR.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.