brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
Evaluate scientific claims and evidence quality. Use for assessing experimental design validity, identifying biases and confounders, applying evidence grading frameworks (GRADE, Cochrane Risk of Bias), or teaching critical analysis. Best for understanding evidence quality,
Claude Code
$ npx -y skills add spacering-net/codeg --skill scientific-critical-thinking --agent claude-code
Codex
$ npx skills add spacering-net/codeg --skill scientific-critical-thinking -a codex -y
Cursor
$ npx skills add spacering-net/codeg --skill scientific-critical-thinking -a cursor -y
Gemini CLI
$ npx skills add spacering-net/codeg --skill scientific-critical-thinking -a gemini-cli -y
GitHub Copilot
$ npx skills add spacering-net/codeg --skill scientific-critical-thinking -a github-copilot -y
OpenCode
$ npx skills add spacering-net/codeg --skill scientific-critical-thinking -a opencode -y
Windsurf
$ npx skills add spacering-net/codeg --skill scientific-critical-thinking -a windsurf -y
name: scientific-critical-thinking description: Evaluates scientific claims and evidence quality. Applies to experimental design validity, biases and confounders, statistical interpretation, evidence grading frameworks (GRADE, Cochrane Risk of Bias), and teaching critical analysis. Supports evidence appraisal and identifying flaws; formal peer review writing belongs to peer-review. allowed-tools: Read Write Edit license: MIT license compatibility: Analytical guidance needs no network. Optional figures via the scientific-schematics skill require OPENROUTER_API_KEY and outbound API access to OpenRouter. metadata: version: "1.5" last-reviewed: "2026-10-01" skill-author: K-Dense Inc.
Critical thinking is a systematic process for evaluating scientific rigor. Assess methodology, experimental design, statistical validity, biases, confounding, and evidence quality using GRADE and Cochrane ROB frameworks. Apply this skill for critical analysis of scientific claims.
This skill should be used when:
1. **Fix the question and unit.** Record population, intervention/exposure, comparator, outcome, time point, effect measure, and target setting. Distinguish descriptive, predictive, and causal claims. Identify the independent experimental/sampling unit. 2. **Extract evidence before judging.** Locate the numerical result, uncertainty, denominators, protocol/registration, analysis plan, and relevant supplementary material. Keep missing reporting separate from evidence that a procedure was not performed. 3. **Assess design and analysis.** Check selection, confounding, measurement, attrition, multiplicity, dependence, and model assumptions. Good fit or optimizer convergence does not establish a uniquely identified parameter or a causal effect. 4. **Choose the right appraisal framework.** Reporting completeness, risk of bias, and certainty of a body of evidence answer different questions. Record the exact tool version and the result being assessed; do not turn checklist counts into a quality score. 5. **Synthesize with scope intact.** Examine independent replication, overlapping samples, missing evidence, and applicability. Apply GRADE per outcome/comparison when appropriate, with explicit domain reasons, rather than grading a whole paper by its design label. 6. **Write a traceable critique.** For each concern give the source location, observation, consequence for the claim, uncertainty, and a feasible remedy. Separate supported conclusions from assumptions and from clinical/policy recommendations.
Current framework versions, primary sources, and verification limits are in [references/review_sources.md](references/review_sources.md). The examples in the references are teaching examples, not empirical findings or validated patient-specific advice.
Only add figures when the **user explicitly requests** a diagram (for example, a GRADE flowchart, bias decision tree, or evidence-quality framework).
**When figures help:**
**How to create figures:**
Run from the repository root, with `OPENROUTER_API_KEY` set:
python skills/scientific-schematics/scripts/generate_schematic.py "Illustrative GRADE appraisal: define outcome and comparison, assess certainty domains with reasons; keep recommendation decisions separate" -o figures/grade_flowchart.png --doc-type report
This optional command's CLI was checked with `--help`; paid generation was not exercised for this example. Follow that skill's current dependencies and review every generated label.
**Disclosure:** AI schematic generation sends your prompt to [OpenRouter](https://openrouter.ai/) (a third-party API). Do not include unpublished sensitive details unless that transmission is appropriate for your project.
---
Seven capability areas, each with the questions to ask and what the answers imply, are in [references/core_capabilities.md](references/core_capabilities.md):
1. **Methodology critique** — design, controls, confounding, and whether the method can answer the question asked. 2. **Bias detection** — selection, measurement, publication, and cognitive biases. 3. **Statistical analysis evaluation** — power, multiplicity, p-value misuse, effect sizes. 4. **Evidence quality assessment** — study hierarchy, replication, and strength of inference. 5. **Logical fallacy identification** — the fallacies that recur in scientific argument. 6. **Research design guidance** — how to strengthen a design before data collection. 7. **Claim evaluation** — separating what was shown from what is being asserted.
Per-topic detail is in [references/scientific_method.md](references/scientific_method.md), [references/common_biases.md](references/common_biases.md), [references/statistical_pitfalls.md](references/statistical_pitfalls.md), [references/evidence_hierarchy.md](references/evidence_hierarchy.md), [references/logical_fallacies.md](references/logical_fallacies.md), and [references/experimental_design.md](references/experimental_design.md).
1. **Be Constructive**
Collaborative multi-agent AI coding workspace: aggregate sessions from Claude Code, Codex, OpenCode, Pi, Grok Build, etc. Desktop app, self-hosted server, or Docker.
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
Use when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor…
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline…
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically…
Personalized audit that teaches the advanced Paradev (formerly Superset) features the user isn't using yet (automations, parallel…
Direct actions on one Orchestrator session or PR: stop or interrupt, resume, merge a PR, start a review, screenshot a session's…
Your capability catalog — read this at boot. Lists the temporal date-range skills and the external integrations (reached via the…