Help us improve
Share bugs, ideas, or general feedback.
From skills-for-humanity
Runs a complete logical analysis on any argument, plan, or reasoning — validates premises, tests inferences, detects fallacies, and surfaces hidden assumptions.
npx claudepluginhub human-avatar/skills-for-humanityHow this skill is triggered — by the user, by Claude, or both
Slash command
/skills-for-humanity:logic-checkThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
An argument can fail in three distinct places: a premise can be false, the inference can be invalid (the conclusion doesn't follow even if premises are true), or a hidden assumption can be doing load-bearing work without being examined. Most reasoning errors are invisible because they happen in exactly these places. A complete logic check must test all three.
Validates whether an argument's premises support its conclusion and identifies logical fallacies. Use when reviewing design decisions, technical proposals, or any reasoning that needs scrutiny.
Analyzes claims by mapping arguments, auditing evidence quality, detecting logical fallacies and biases, and issuing verdicts. For evaluating research or technical arguments.
Stress-tests ideas, plans, and decisions using structured critical reasoning across 5 modes (Socratic, dialectic, pre-mortem, red team, falsification).
Share bugs, ideas, or general feedback.
An argument can fail in three distinct places: a premise can be false, the inference can be invalid (the conclusion doesn't follow even if premises are true), or a hidden assumption can be doing load-bearing work without being examined. Most reasoning errors are invisible because they happen in exactly these places. A complete logic check must test all three.
Step 1: Extract the Argument Structure Identify the premises (claims taken as given), the inference (how they connect), and the conclusion (what is claimed to follow). Write them out explicitly. Complex reasoning often has multiple linked arguments — map the chain.
Step 2: Test Each Premise Classify each premise:
The argument is only as strong as its weakest load-bearing premise.
Step 3: Test the Inference Even if all premises are true: does the conclusion follow? Test with a steelman of the denial — can the premises all be true and the conclusion still be false? If yes, the inference is invalid. Common inference failures: missing variables, scope shifts (all → some), correlation treated as causation.
Step 4: Scan for Fallacies Name any fallacies present specifically — do not give a generic list. Common ones in strategic and analytical reasoning: hasty generalisation, false dilemma, straw man, appeal to authority, ad hominem, sunk cost, post hoc ergo propter hoc, false analogy, slippery slope.
Step 5: Surface Hidden Assumptions What must be true for the argument to work — but is never stated? These are the most dangerous load-bearers because they are not examined. Ask: "What would have to be true for this to hold? Is it?"
Step 6: Assess Overall Does the reasoning hold? Give a verdict and name the specific weaknesses if it doesn't.
Before proceeding, use the AskUserQuestion tool:
Proceed based on their selection.
Premises:
Inference: [How the premises are claimed to connect to the conclusion]
Conclusion: [What is claimed to follow]
| Premise | Classification | Notes |
|---|---|---|
| P1 | Established / Assumption / Contested / Unsupported | ... |
| P2 | ... | ... |
Valid: Yes / No / Partially Analysis: [Does the conclusion follow from the premises? Where does the inference fail if it does?]
The reasoning: Holds / Has specific problems / Does not hold
Specific problems (if any):
Use logic-council when the situation requires adversarial peer challenge between logical positions. Use logic-argument-validation for a single, focused argument. This skill covers complete reasoning chains — plans, proposals, analyses — in a single pass.
After delivering this output, use AskUserQuestion to offer the next move:
/logic-fixer — Fix the specific problems the check identified/constraint-hardness-testing — Test whether the flaws are hard constraints or soft assumptions/decision-premortem-analysis — Stress-test the plan the reasoning supports