S4h Logic Argument Validation
Check whether an argument's premises actually support its conclusion, and identify logical fallacies. Use when reviewing a design decision, technical proposal, product argument, or any reasoning where the conclusion needs to hold up under scrutiny. TRIGGERS: 'validate this argument', 'does this logic hold', 'check my reasoning', 'is this a fallacy', 'find the flaw in this', any proposal or decision where the reasoning chain matters. Pairs well with logic-consistency-check when a full document needs scrutiny.
Install
npx skills add human-avatar/skills-for-humanity --skill s4h-logic-argument-validationgit clone --depth 1 https://github.com/human-avatar/skills-for-humanity.git /tmp/skills-for-humanity
mkdir -p ~/.claude/skills
cp -r /tmp/skills-for-humanity/skills/s4h-logic-argument-validation ~/.claude/skills/s4h-logic-argument-validationPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Logic Argument Validation An argument can *sound* compelling while the reasoning is broken. Confident language, plausible premises, a conclusion that feels right — none of these guarantee the argument actually holds. This skill validates the structure: do the premises support the conclusion, and is the reasoning free of fallacies? --- ## Your Process **Step 1: Extract the argument structure** Before evaluating, make the argument explicit: - **Premises**: what claims is the argument built on? - **Conclusion**: what is it trying to prove? - **Reasoning**: what's the logical path from premises to conclusion? Restate this clearly before proceeding. Often the weakest point becomes obvious once the structure is explicit. **Framing check:** Confirm the argument being examined and the claim at stake before continuing. State what you've identified — the actual argument and the conclusion it is trying to establish — in one sentence, then use `AskUserQuestion`: - **Question:** "I'm reading this as: [your one-sentence framing of the argument and its conclusion]. Is that right?" - **Header:** "Framing" - **Options:** - **Yes — proceed** — framing is correct - **Adjust** — one element is off; user will correct it before you continue - **Reframe** — different situation than read; incorporate the correction before proceeding **Step 2: Test premise soundness** For each premise: - Is it stated as fact? Is it actually established, assumed, or contested?
Details
- Skill name
s4h-logic-argument-validation- Repository
- human-avatar/skills-for-humanity
- Path
skills/s4h-logic-argument-validation/SKILL.md- License
- MIT
- Repo updated
- 15 July 2026
- Listed in
- BehiSecc/awesome-claude-skills
FAQ
What does the S4h Logic Argument Validation skill do?
Check whether an argument's premises actually support its conclusion, and identify logical fallacies. Use when reviewing a design decision, technical proposal, product argument, or any reasoning where the conclusion needs to hold up under scrutiny. TRIGGERS: 'validate this argument', 'does this logic hold', 'check my reasoning', 'is this a fallacy', 'find the flaw in this', any proposal or decision where the reasoning chain matters. Pairs well with logic-consistency-check when a full document needs scrutiny.
How do I install the S4h Logic Argument Validation skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add human-avatar/skills-for-humanity --skill s4h-logic-argument-validation. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is S4h Logic Argument Validation popular?
It lives in human-avatar/skills-for-humanity, which has 242 GitHub stars and 25 forks, and is included in 1 curated skill list.
Related skills
S4h
242human-avatar/skills-for-humanity
Master orchestration skill. Takes any situation in plain English, identifies the underlying goal, designs a multi-skill reasoning workflow, and executes it sequentially — feeding each skill's output into the next. Use when you say 'help me think through this', 'I need to figure out what to do', 'where do I start', or any time you want structured thinking applied end-to-end rather than routed to a single tool.
S4h Aesthetic
242human-avatar/skills-for-humanity
Entry point for the aesthetic toolkit. Routes to the right aesthetic skill based on your situation. Use when you say 'aesthetic', 'check the design', 'does this feel right', 'is this elegant', 'is this too complex', 'what pattern is this', 'find the simpler version', or want an aesthetic lens applied without knowing which specific tool fits.
S4h Aesthetic Coherence Check
242human-avatar/skills-for-humanity
Tests whether the parts of something form a unified whole — finding the jarring inconsistencies that accumulate when different contributors work without a shared vision. TRIGGERS: 'coherence check', 'does this feel unified', 'something feels off', 'inconsistent', 'check the whole', 'does this hang together'.
S4h Logic Causality Mapping
242human-avatar/skills-for-humanity
Map causal relationships, trace dependencies, and reason about consequences before acting. Use when you need to understand what causes what, what breaks if something changes, or what must be true for a plan to work. TRIGGERS: 'map the dependencies', 'what causes this', 'what breaks if I change X', 'trace the root cause', 'if X then what', 'what has to be true for this to work', any situation involving root cause analysis, impact assessment, dependency tracing, or reasoning about chains of effect.
S4h Logic
242human-avatar/skills-for-humanity
Entry point for the logic toolkit. Routes to the right logic skill based on your situation. Use when you say 'logic', 'is this sound', 'check my reasoning', 'find the flaw', 'fix this argument', 'find contradictions', 'map the dependencies', 'map the constraints', or want logical analysis applied without knowing which specific tool fits.
S4h Logic Constraint Mapping
242human-avatar/skills-for-humanity
Map the full constraint landscape for a decision, design, or plan — distinguishing hard limits from soft preferences, surfacing hidden constraints, and finding conflicts between them. Use before committing to an approach, when a plan keeps hitting unexpected walls, or when it's unclear what's actually negotiable. TRIGGERS: 'map the constraints', 'what are we actually working with', 'what's blocking this', 'what can we change', 'constraint analysis', any situation where the boundaries of what's possible need to be understood before proceeding.
Browse the most popular Claude skills, all other skills, or write your own with the skills generator.