Correlation walked in; make it prove causation. Use when someone claims "X causes Y" from observational data, asks "did the change actually cause the improvement?", "is this confounded?", "what would have happened if we hadn't shipped it?", plans an A/B test, or investigates why an incident/outbreak spread the way it did.
How this skill is triggered — by the user, by Claude, or both
Slash command
/zetetic-team-subagents:causal-auditThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
**Problem shape:** a causal claim is being made, tested, or acted on, and the
Problem shape: a causal claim is being made, tested, or acted on, and the evidence is correlational, confounded, unreplicated, or resisted by the organization even when clean. The move: make the causal structure explicit, then intervene or design the comparison that could refute it.
| Agent | Use when |
|---|---|
| pearl | "X causes Y" claimed from correlation; counterfactual questions; controlled-for variables may be colliders — draw the DAG first |
| fisher | an experiment is being designed: randomize, block, replicate, factorial over one-at-a-time; "run it and see" needs a design document |
| peirce | surprising observation needs candidate explanations; several hypotheses and a limited budget — test cheapest-to-refute first |
| semmelweis | matched groups with wildly different outcomes; the evidence is clear but the institution resists it |
| snow | something is spreading (bug, outage class, behavior) — outbreak investigation, case definitions, Hill's criteria |
| mill | only a handful of cases exist — methods of agreement/difference, necessary vs sufficient conditions |
| feinstein | diagnosis under uncertainty: differential ranked by likelihood ratios, treatment thresholds before acting |
tools/genius-invoker.sh route "<problem>" and take the top ranked match.tools/genius-invoker.sh invoke <agent> "<problem>", then read
agents/genius/<agent>.md in full.<workflow> step by step and answer in its
<output-format>. State explicitly which rung of the ladder (association /
intervention / counterfactual) the final claim sits on.tools/genius-invoker.sh compose pearl fisher -- "<problem>".npx claudepluginhub cdeust/cortex --plugin zetetic-team-subagentsGuides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Enforces test-driven development: write failing test first, then minimal code to pass. Use when implementing features or bugfixes.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.