From skills-for-humanity
Maps a belief's justification structure (foundationalist, coherentist, reliabilist) and identifies the weakest evidential link. Useful when examining assumptions, repeated evidence, or unsupported certainty.
How this skill is triggered — by the user, by Claude, or both
Slash command
/skills-for-humanity:s4h-epistemology-justificationThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
A belief can feel well-supported without actually being justified. The feeling of certainty is not evidence of justification — it's evidence of confidence, which is a psychological state, not an epistemic one. Justification analysis makes the load-bearing structure of a belief explicit so it can be examined and tested.
A belief can feel well-supported without actually being justified. The feeling of certainty is not evidence of justification — it's evidence of confidence, which is a psychological state, not an epistemic one. Justification analysis makes the load-bearing structure of a belief explicit so it can be examined and tested.
Three main structures for how beliefs get justified:
Most real belief systems are hybrid. The point of analysis is not to pick the right theory of justification — it's to find where the specific belief's justification structure is weakest.
Step 1: Identify the Belief State the belief precisely. What exactly is being claimed to be known or justifiably believed? Strip away hedges and weasel words to get the core claim.
Framing check: Confirm the specific belief before continuing. State what you've identified — the actual claim being analyzed and the domain or context it comes from — in one sentence, then use AskUserQuestion:
Step 2: Trace the Justification Chain Ask: "What makes you think that?" Recursively trace the answer until you hit one of three stopping points:
Write out the chain explicitly. Many chains are assumed rather than traced — making them explicit is half the work.
Step 3: Classify the Justification Structure
| Structure | Signature | Key question to test it |
|---|---|---|
| Foundationalist | Chain traces back to a basic belief | Is that basic belief actually self-evident, or just assumed? |
| Coherentist | Beliefs support each other mutually | Is the web genuinely independent, or are all the beliefs downstream of one hidden assumption? |
| Reliabilist | Justified by process quality | Is the process actually reliable in this domain? Are there known failure modes? |
Most real cases are hybrid — identify which structure dominates at each link.
Step 4: Test Each Link
For each step in the justification chain, ask:
Classify each link: sound / shaky / unsupported / circular.
Special flag: circular justification — where A justifies B and B justifies A, without either being independently grounded. Common in self-reinforcing organizational beliefs ("our strategy is working because our metrics are up; our metrics are up because our strategy is working").
Step 5: Identify the Weakest Link
Before narrowing: Show the complete link assessment to the user first. Use AskUserQuestion:
Which link, if removed, would most damage justification for the belief? This is the critical point — the place where effort to strengthen or challenge the belief will have the most leverage.
Step 6: Assess Overall Justification Given the chain and its weakest link:
Step 7: What Would Change the Justification? What evidence, argument, or process change would most improve justification? What would undermine it? The mark of a well-justified belief is that you can say precisely what would change 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.
[Precise statement of what's being analyzed]
Chain terminates at: [Basic belief / Mutual coherence web / Process trust]
Primary structure: Foundationalist / Coherentist / Reliabilist / Hybrid Notes: [One sentence on why]
| Link | Type | Assessment | Notes |
|---|---|---|---|
| [Link 1] | Foundation / Inference / Process | Sound / Shaky / Unsupported / Circular | [Why] |
| [Link 2] | ... | ... | ... |
The critical point: [Specific link] Why it's critical: [What depends on it; what breaks if it fails]
Assessment: Justified / Unjustified / Underdetermined Reasoning: [One paragraph]
Would strengthen: [Specific evidence, argument, or process] Would undermine: [Specific evidence, argument, or process]
Use epistemology-knowledge-types first if you're not sure what kind of claim you're dealing with — the justification structure depends on the knowledge type. Use epistemology-epistemic-status when you need to assess confidence across many claims in a domain, not just one belief. Use logic-check when the issue is inference validity (does the conclusion follow?) rather than justification (is the belief grounded?).
After delivering this output, use AskUserQuestion to offer the next move:
/s4h-logic-argument-validation — Validate the logical structure of the justifications/s4h-investigation-source-trace — Trace justifications back to their original sources/s4h-epistemology-limits — Find where justification runs out and uncertainty beginsnpx claudepluginhub human-avatar/skills-for-humanityAudits claims in a domain by assigning explicit epistemic statuses (known, believed, assumed, hoped) to separate confidence from correctness.
Analyzes claims by mapping arguments, auditing evidence quality, detecting logical fallacies and biases, and issuing verdicts. For evaluating research or technical arguments.
Exposes Claude's reasoning chain as an auditable, decomposable artifact. Quick mode yields assumption inventory and weakest link; full mode adds decision branching, confidence decomposition, and falsification conditions.