Install
$ agentstack add skill-skyf0xx-better-thinking-evidence-hierarchy ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
About
Evidence Hierarchy
Rank the available evidence by its strength for the specific claim class — because evidence types have different power for different kinds of questions.
Why
Anecdote, expert opinion, observational data, and experiment differ by orders of magnitude in reliability — but the ranking itself depends on the question (an RCT is gold for "does it work on average"; a mechanism study is better for "will it work here"). Explicit ranking stops the vivid from beating the valid.
Use when / Don't use when
- Use when: evidence conflicts; a decision leans on "studies show" or "experts say"; synthesizing mixed material.
- Don't use when: all evidence is one type — assess quality within type instead.
Inputs → Outputs
- Inputs: a claim plus a pile of heterogeneous evidence.
- Outputs: the evidence sorted by strength-for-this-claim, with the verdict weighted accordingly.
Principles
- For causal claims: experiments > natural experiments > controlled observational > raw correlational > anecdote — within each tier, quality still varies hugely.
- For existence claims, one good observation suffices; for "typical case" claims, representative sampling beats any single study.
- Expert opinion is evidence about judgment under uncertainty, strong only where the expert has feedback-rich experience.
- The hierarchy ranks types — a flawed RCT loses to a strong cohort study;
methodology-critiqueadjudicates within-type quality.
Procedure
- Classify the claim: causal, existence, frequency, predictive, or normative.
- Sort evidence into types; note the appropriate hierarchy for this claim class.
- Within each type, spot-check quality — sample, method, independence.
- Weight the verdict by the top-tier evidence; use lower tiers only to fill gaps the top tier doesn't cover (external validity, mechanisms, edge cases).
- Note the mismatches: strong evidence for a nearby claim being marketed as evidence for this claim.
- Report the verdict, the evidence carrying it, and what missing evidence tier would settle it as residual uncertainty.
Common mistakes
- Treating the hierarchy as absolute rather than claim-relative.
- Letting twenty anecdotes outvote one experiment.
- The bait-and-switch in step 5 — efficacy evidence sold as effectiveness evidence.
- Dismissing anecdotes entirely — they're hypothesis generators and existence proofs, just not verdict-carriers.
Examples
- Drug efficacy: trial data outweighs clinician impressions.
- "Remote work hurts productivity" — asking what evidence type even bears on the claim before weighing any of it.
- An architecture choice supported by one blog post versus real benchmark data.
Related
- [[methodology-critique]] — audits quality within a tier; this skill ranks across tiers.
- [[statistical-audit]] — the number-level audit once a quantitative study is chosen as evidence.
- [[bayesian-updating]] — consumes the weighted verdict to update belief.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: skyf0xx
- Source: skyf0xx/better-thinking
- License: MIT
- Homepage: https://zenbin.org/p/better-thinking
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.