From skills-for-humanity
Generates rival hypotheses that could explain the same observations, helping avoid confirmation bias. Use when you have a claim or explanation and want to test whether something else could account for the evidence.
How this skill is triggered — by the user, by Claude, or both
Slash command
/skills-for-humanity:s4h-investigation-counter-hypothesisThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
The confirmation trap is automatic: once we have an explanation, we look for evidence that supports it and stop looking for evidence that would support alternatives. Counter-hypothesis generation is the structural antidote. The process is not to argue against your explanation — it is to seriously generate the best competing explanations and then ask: given all the evidence, which hypothesis sho...
The confirmation trap is automatic: once we have an explanation, we look for evidence that supports it and stop looking for evidence that would support alternatives. Counter-hypothesis generation is the structural antidote. The process is not to argue against your explanation — it is to seriously generate the best competing explanations and then ask: given all the evidence, which hypothesis should I actually believe? The decisive test — the observation that, if run, would most clearly discriminate between hypotheses — is the product.
Step 1: State the Hypothesis Under Investigation Write out the claim or explanation you are currently working with:
Framing check: Confirm the specific hypothesis before continuing. State what you've identified — the claim being tested, what it purports to explain, and what evidence is cited for it — in one sentence, then use AskUserQuestion:
Step 2: Generate Rival Hypotheses Generate rival alternative explanations that could account for the same observations using all the strategies below. Then show the complete generated set to the user before narrowing.
Before narrowing: Show all generated rivals to the user first. Use AskUserQuestion:
Then narrow to 3–5 rivals. Each developed rival hypothesis should:
Strategies for generating rivals:
Do not construct straw man rivals. Generate the most serious version of each alternative.
Step 3: Assess Evidence Fit for Each Rival For each rival hypothesis:
Step 4: Identify the Discriminating Evidence For each pair of hypotheses (original vs. rival), ask: what single observation or piece of evidence would most cleanly rule one out?
If you already have this evidence, apply it. If you don't, name what investigation would produce it.
Step 5: Identify the Decisive Test Across all rivals, identify the single test that would do the most work:
Step 6: Rank Current Credibility Given all available evidence — including evidence for rivals — how does each hypothesis rank? Do not default to your original hypothesis unless the evidence genuinely favors it.
Before proceeding, use the AskUserQuestion tool. State your interpretation of the situation in 1–2 sentences — what is being analyzed and what the core question is — then ask:
Proceed based on their selection. If the user reframes, incorporate the correction before running any analysis.
Observations to explain: [What we're trying to account for] Current hypothesis: [The explanation being tested] Evidence currently supporting it: [What is cited in its favor]
Rival 1: [Name/Description]
Rival 2: [Name/Description] [Same structure]
[Repeat for 3-5 rivals]
| Hypothesis A | Hypothesis B | Discriminating Evidence | Status |
|---|---|---|---|
| Original | Rival 1 | [Observation that distinguishes them] | [Have it / Need to find it] |
| Original | Rival 2 | [Observation that distinguishes them] | [Have it / Need to find it] |
Test: [The single investigation that would do the most work] What it would show: [How it discriminates between hypotheses] Feasibility: [Can it be run? If not, what's the best proxy?]
The live question: [What remains genuinely uncertain and what evidence would resolve it]
Counter-hypothesis generation is not devil's advocacy. The goal is not to argue for an alternative but to seriously evaluate whether the evidence discriminates between competing explanations. Use investigation-evidence-audit to evaluate the strength of the evidence cited for the original hypothesis. Use logic-argument-validation to check whether the inference from evidence to hypothesis is valid. Counter-hypothesis is specifically about rival explanations — not about whether the evidence is good, but about whether it uniquely supports one interpretation.
After delivering this output, use AskUserQuestion to offer the next move:
/s4h-investigation-evidence-audit — Audit evidence for and against each hypothesis/s4h-probability-scenario-weighting — Weight competing hypotheses by probability/s4h-investigation-triangulation — Triangulate across hypotheses to find what holdsnpx claudepluginhub human-avatar/skills-for-humanityPerforms Analysis of Competing Hypotheses (ACH) to evaluate multiple hypotheses against evidence via disconfirmation-focused matrix, diagnosticity, sensitivity analysis, and falsification milestones.
Turns observations into testable hypotheses with predictions, mechanisms, and experiments. Follows scientific method; use for ideation or LLM testing on datasets.
Generates falsifiable, testable research hypotheses from notes and documents. Use when brainstorming hypotheses, generating research questions, or identifying testable predictions. Not for general Q&A.