deductive-reasoning
Skill6 starsChanged 4 months agoApache-2.0View on GitHub
Use when a conclusion must be tested against explicit rules, principles, criteria, policies, definitions, premises, or if-then logic. Use when applying deductive reasoning, rule-based reasoning, premise-to-conclusion testing, logical consistency checks, or validity review.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- zizhenchen47-oss/claude-skillstheir own version, first seen Jun 4, 2026
- THUYRan/Legal-Skills-Chinesetheir own version, first seen May 23, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- THUYRan/Legal-Skills-Chinese★ 867same name
- zizhenchen47-oss/claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository57 other files it gives its agents.
- 5w1h-analysisSkill
- abductive-reasoningSkill
- account-planSkill
- affinity-diagramSkill
- assumption-inventorySkill
- balanced-scorecardSkill
- break-even-analysisSkill
- business-model-canvasSkill
- change-event-timelineSkill
- change-impact-analysisSkill
- communications-planSkill
- competitive-positioningSkill
- constraint-analysisSkill
- cost-benefit-analysisSkill
- critical-uncertaintiesSkill
- customer-segmentationSkill
- customer-success-health-scoreSkill
- deal-strategy-mapSkill
- decision-matrixSkill
- effort-impact-matrixSkill
- empathy-mapSkill
- evidence-mapSkill
- fifteen-percent-solutionsSkill
- first-principles-thinkingSkill
- fishbone-diagramSkill
- five-whys-root-causeSkill
- force-field-analysisSkill
- go-to-market-diagnosisSkill
- hypothesis-treeSkill
- inductive-reasoningSkill
- issue-treeSkill
- jobs-to-be-doneSkill
- kano-modelSkill
- mece-frameworkSkill
- metrics-treeSkill
- mind-map-analysisSkill
- min-specsSkill
- north-star-metricSkill
- pestel-analysisSkill
- porter-five-forcesSkill
- power-interest-gridSkill
- pre-mortemSkill
- pricing-strategy-checkSkill
- raci-matrixSkill
- rice-scoringSkill
- risk-matrixSkill
- scenario-planningSkill
- service-blueprintSkill
- signal-vs-noise-filterSkill
- stakeholder-power-mapSkill
- swot-analysisSkill
- systems-thinkingSkill
- user-journey-mappingSkill
- validation-planSkill
- weighted-scorecardSkill
- win-loss-reviewSkill
- wsjf-prioritizationSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 4 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
Use this skill to test whether a conclusion follows from stated premises, rules, or criteria.
- Very specific: line 28
If an input is missing, mark it as missing, state the assumption used, and add a validation action.
- Very specific: line 32
Do not use when there are no clear premises or rules and the task is pattern discovery.
- Distinctive: line 72
Do not treat an assumption as a rule.
- Distinctive: line 73
Do not hide weak premises inside confident logic.
- Distinctive: line 76
Use plain wording so the conclusion can be challenged or reused.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Deductive Reasoning
Use this skill to test whether a conclusion follows from stated premises, rules, or criteria.
Method Notes
- Deductive reasoning moves from general rules or premises to a specific conclusion.
- A deductive conclusion is only as reliable as the premises and the logic connecting them.
- This method is strongest when rules, definitions, criteria, or constraints are explicit.
- It should separate validity from truth: an argument can be logically valid but built on a false or weak premise.
Required Inputs
Collect or infer these inputs before execution:
- conclusion or decision to test
- stated rules, criteria, principles, policies, or premises
- facts of the specific case
- scope boundary
- exceptions or override conditions
If an input is missing, mark it as missing, state the assumption used, and add a validation action.
When Not To Use
Do not use when there are no clear premises or rules and the task is pattern discovery. Use inductive-reasoning, abductive-reasoning, or affinity-diagram first.
Step-by-Step Execution
| Step | Required input | How to execute | Output |
| State the conclusion | Decision, claim, or recommendation. | Write the conclusion in one testable sentence. | Conclusion to test. |
| List premises | Rules, criteria, policies, principles, definitions. | Separate general premises from case-specific facts. | Premise list. |
| Check premise quality | Source, evidence, authority, scope. | Mark each premise as strong, medium, weak, or missing. | Premise quality table. |
| Map logic chain | Premises, case facts, conclusion. | Build the if-then path from premises to conclusion. | Logic chain. |
| Test validity | Logic chain, exceptions. | Check whether the conclusion necessarily follows if premises are true. | Validity judgment. |
| Check exceptions | Scope, edge cases, override conditions. | Identify conditions that weaken or reverse the conclusion. | Exception list. |
| Rewrite conclusion | Validity and premise quality. | State a careful conclusion that matches the actual logic strength. | Revised conclusion. |
Output Template
### 1. Conclusion To Test
- Claim / decision:
- Scope:
### 2. Premise Table
| Premise | Type | Evidence / source | Strength | Scope limit |
|---|---|---|---|---|
| | rule / criterion / principle / fact / assumption | | strong / medium / weak / missing | |
### 3. Logic Chain
1.
2.
3.
### 4. Validity Check
- Does the conclusion follow if the premises are true?
- Weakest premise:
- Exception or edge case:
- Revised conclusion:Quality Gate
- Do not treat an assumption as a rule.
- Do not hide weak premises inside confident logic.
- Separate logical validity from real-world truth.
- Identify exceptions and scope limits.
- Use plain wording so the conclusion can be challenged or reused.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

