Individual skill
s4h-investigation-counter-hypothesis
Generates the best alternative explanations for the same observations. Use when you have a claim or explanation and want to know whether something else could explain the evidence just as well — 'could there be another explanation', 'what else could cause this', 'am I sure this isn't something else', 'steel-man the alternative', 'what would a skeptic say', 'rival hypotheses'.
skills/s4h-investigation-counter-hypothesis/SKILL.md
Source commit a30df8b67698ccb03ef5e35d68c2eddc5321ad3f
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- Last checked
- Nov 5, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 240
- Repository last updated
- Jul 15, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- claude-code Repository topic
- claude-code-plugin Repository topic
- cognitive-frameworks Repository topic
- creativity Repository topic
- decision-making Repository topic
- ethics Repository topic
- mental-models Repository topic
- problem-solving Repository topic
- reasoning Repository topic
- systems-thinking Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 8,679 bytes
Read excerpt
# Investigation: Counter-Hypothesis
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.
---
## Your Process
**Step 1: State the Hypothesis Under Investigation**
Write out the claim or explanation you are currently working with:
- What is being explained? (The observations, pattern, or outcome)
- What does the hypothesis assert is causing, driving, or explaining it?
- What evidence is currently cited in support?