reviewer-2

Solid

Adopt a critical-reviewer stance to stress-test a claim, result, or manuscript section. For each claim: identify the baseline being compared against, name the counterfactual, surface plausible alternative explanations, and check that stated uncertainty is consistent with the strength of the claim. Use this whenever the user asks to be challenged, invokes "Skeptic," "Reviewer #2," "red team," "poke holes," "what am I missing," or wants a result/argument/section stress-tested before submission — even without those exact words. Reports concerns; does not rewrite the user's argument.

Code & Development 61 stars 5 forks Updated yesterday MIT

Install

View on GitHub

Quality Score: 87/100

Stars 20%
60
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

## Stance Adversarial, not agreeable. Surfacing weakness is the function. Do not soften findings. Read the material fresh. Do not carry the user's framing into the review — treat author intent as irrelevant to whether the claim holds. If the user supplies an inline mode definition in the conversation, adopt that stance fully over these defaults. ## Per-claim analysis For each claim: - **Baseline** — what is being compared against (e.g., pre-industrial frequency, late-20th-century mean) - **Counterfactual** — what the result looks like under natural forcing only, or absent the intervention - **Alternative explanations** — plausible competing interpretations (e.g., urban heat island, land-use change, multidecadal variability) - **Uncertainty consistency** — does stated confidence match the strength of the claim? (yes/no + why) Example: *"Heat extremes in the Southwest are more frequent due to climate change."* - Baseline: late-20th-century event frequency - Counterfactual: frequency under natural forcing only - Alternatives: urban heat island; land-use change; multidecadal variability (AMO/PDO) - Uncertainty: is stated confidence consistent with formal attribution literature? ## Anti-Rationalization | Excuse | Reality | |---|---| | "This claim looks well-supported" | Did I name the specific counterfactual, or just gesture at it? | | "The confidence sounds right" | Did I check stated uncertainty against what formal attribution requires, not just the prose framing? | | "...

Details

Author
dgilford
Repository
dgilford/ai-science-toolkit
Created
3 months ago
Last Updated
yesterday
Language
Shell
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Listed

research-critic

Use AT EVERY RESEARCH STEP (hypothesis design, experiment setup, result interpretation, conclusion writing) to challenge soundness BEFORE committing the step. Catches confirmation bias, p-hacking, leakage, weak baselines, ungrounded claims, ad-hoc thresholds, survivorship bias. Apply automatically whenever about to write a paper claim, design an ablation, interpret a number, or update a results doc. Pairs with code-verifier (which audits artifact authenticity).

1 Updated 3 weeks ago
jajupmochi
AI & Automation Listed

skeptic

Adversarial reviewer that challenges whether something should be built at all, before challenging how. Use when asked to be a skeptic, "be skeptical", "pressure-test this", "poke holes in this", "play devil's advocate", or "should we even build this?". Applies a blunt YAGNI / over-engineering / scope critique to any artifact, a plan, a design, requirements, a feature request, or code. Complements correctness and security review, which ask whether something is built right; the skeptic asks whether it should exist.

1 Updated 3 days ago
maccydee
Code & Development Listed

swing-review

Devil's Advocate stress-testing for code, architecture, PRs, and decisions. Surfaces hidden flaws through structured adversarial analysis with metacognitive depth. Use for high-stakes review, stress-testing choices, or when the user wants problems found deliberately. NOT for routine code review (use engineering:code-review). Triggers on "스트레스 테스트", "stress test", "devil's advocate", "반론", "이거 괜찮아", "문제 없을까", "깊은 리뷰", "critical review", "adversarial".

1 Updated 2 days ago
SURFLIN2030