reviewer-2
SolidAdopt 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.
Install
Quality Score: 87/100
Skill Content
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
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).
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.
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".