agentleFS
fzfcleefzfclee/consulting-skills/skills/inductive-reasoning/SKILL.md

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

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
  1. Distinctive:

    Use this skill to infer a likely pattern or general rule from observed evidence.

    line 9
  2. Very specific:

    If an input is missing, mark it as missing, state the assumption used, and add a validation action.

    line 28
  3. Very specific:

    Do not use when the conclusion must follow from formal rules or fixed criteria.

    line 32
  4. Distinctive:

    Do not overgeneralize from a thin or biased sample.

    line 73
  5. Distinctive:

    Look for exceptions before writing the conclusion.

    line 74
  6. Distinctive:

    Keep the boundary of the generalization explicit.

    line 76

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

StepRequired inputHow to executeOutput
Define the inference questionDecision context, target population.State what pattern or generalization is being tested.Inference question.
List observationsCases, data points, quotes, events.Put each observation in a separate row with source and timing.Observation table.
Cluster patternsObservation table.Identify repeated behaviors, causes, needs, outcomes, or signals.Pattern candidates.
Test strengthSample size, representativeness, consistency.Rate each pattern by frequency, diversity of support, and evidence quality.Pattern strength table.
Look for exceptionsKnown counterexamples, missing segments.Identify observations that contradict or limit the pattern.Exception list.
State likely generalizationPattern strength and exceptions.Write the conclusion with confidence and boundary conditions.Inductive conclusion.
Define validationWeakest 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.