inductive-reasoning
Skill6 starsChanged 4 months agoApache-2.0View on GitHub
Use when patterns, trends, generalizations, or likely rules must be inferred from examples, cases, observations, data points, interviews, events, or repeated signals. Use when applying inductive reasoning, pattern inference, evidence-to-generalization synthesis, or trend interpretation.
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
- deductive-reasoningSkill
- 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
- 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 infer a likely pattern or general rule from observed evidence.
- 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 the conclusion must follow from formal rules or fixed criteria.
- Distinctive: line 73
Do not overgeneralize from a thin or biased sample.
- Distinctive: line 74
Look for exceptions before writing the conclusion.
- Distinctive: line 76
Keep the boundary of the generalization explicit.
≈ “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
Inductive Reasoning
Use this skill to infer a likely pattern or general rule from observed evidence.
Method Notes
- Inductive reasoning moves from specific observations to a broader pattern or generalization.
- Inductive conclusions are probabilistic, not certain.
- The method should make sample size, representativeness, exceptions, and confidence visible.
- It is useful for customer research, repeated stakeholder behavior, market signals, operational symptoms, and trend interpretation.
Required Inputs
Collect or infer these inputs before execution:
- observations, examples, cases, data points, quotes, or events
- source and timing of observations
- population or context being generalized to
- known exceptions
- decision or hypothesis the pattern will inform
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 the conclusion must follow from formal rules or fixed criteria. Use deductive-reasoning instead.
Step-by-Step Execution
| Step | Required input | How to execute | Output |
| Define the inference question | Decision context, target population. | State what pattern or generalization is being tested. | Inference question. |
| List observations | Cases, data points, quotes, events. | Put each observation in a separate row with source and timing. | Observation table. |
| Cluster patterns | Observation table. | Identify repeated behaviors, causes, needs, outcomes, or signals. | Pattern candidates. |
| Test strength | Sample size, representativeness, consistency. | Rate each pattern by frequency, diversity of support, and evidence quality. | Pattern strength table. |
| Look for exceptions | Known counterexamples, missing segments. | Identify observations that contradict or limit the pattern. | Exception list. |
| State likely generalization | Pattern strength and exceptions. | Write the conclusion with confidence and boundary conditions. | Inductive conclusion. |
| Define validation | Weakest evidence gaps. | Specify what additional evidence would strengthen or weaken the pattern. | Validation plan. |
Output Template
### 1. Inference Question
- What we are trying to infer:
- Population / context:
- Decision use:
### 2. Observation Table
| Observation | Source | Timing | Supports which pattern | Notes |
|---|---|---|---|---|
| | | | | |
### 3. Pattern Candidates
| Pattern | Supporting observations | Exceptions | Confidence | Boundary |
|---|---|---|---|---|
| | | | high / medium / low | |
### 4. Inductive Conclusion
- Likely pattern:
- What it does not prove:
- What would strengthen it:
- What would weaken it:Quality Gate
- Do not overgeneralize from a thin or biased sample.
- Look for exceptions before writing the conclusion.
- State confidence as probability, not certainty.
- Keep the boundary of the generalization explicit.
- Preserve the link between conclusion and observations.
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.

