mcpbeat Sign in

Ladder Of Inference Reflection Agent Skill

Slow down interpretation from observation to action. Use when students or adults need to examine assumptions in conflict, dialogue, or inquiry.

2k tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
525
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/GarethManning/education-agent-skills --skill ladder-of-inference-reflection

The instruction itself

8 sections, as written by the author

Ladder of Inference Reflection

What This Skill Does

Helps students and adults slow down the movement from observation to interpretation to action. The Ladder of Inference is useful when a person has leapt from limited data to a strong conclusion: "She ignored me because she dislikes me," "Students are lazy," "The school doesn't care," or "The community will never change."

This skill does not tell people their feelings are wrong. It separates what was observed from what was selected, interpreted, assumed, concluded, believed, and done. It then opens alternative ladders and evidence-seeking questions.

Evidence Foundation

The Ladder of Inference is associated with Argyris' work on reasoning, defensive routines, and organisational learning, and was popularised for systems learning through Senge and colleagues. It is especially useful in compassionate systems work because mental models often become visible through the meanings people make from selected data.

Input Schema

Required:

  • Situation: The moment, conflict, decision, or interpretation.
  • Context: Where it happened and who is involved.

Optional:

  • Student level: Age/year group.
  • Current interpretation: What someone currently believes the situation means.
  • Desired use: Reflection, restorative dialogue, bias check, inquiry, staff discussion.

Prompt

You are guiding a Ladder of Inference reflection. Help the user move carefully from observed data to selected data, meanings, assumptions, conclusions, beliefs, and actions.

Inputs:
Situation: {{situation}}
Context: {{context}}
Student level: {{student_level}}
Current interpretation: {{current_interpretation}}
Desired use: {{desired_use}}

Rules:
1. Validate that interpretations can feel real while still being incomplete.
2. Distinguish observable data from selected data and meaning-making.
3. Include at least two alternative ladders that could also fit the observable data.
4. Do not force forgiveness, positivity, or reconciliation.
5. In conflict contexts, protect dignity and safety.
6. End with questions that gather evidence or open dialogue.

Return exactly:

## Ladder of Inference: [Situation]

**Context:** [brief]
**Purpose:** [reflection/dialogue/inquiry]

### Step 1: Observable Data
What someone could have seen/heard/read without interpretation:
- [observable fact]
- [observable fact]

### Step 2: Selected Data
What the person may have noticed most:
- [selected clue]
- [selected clue]

### Step 3: Meanings Added
Possible meanings attached to the selected data:
- [meaning]

### Step 4: Assumptions
Possible assumptions underneath the meaning:
- [assumption]

### Step 5: Conclusions
What the person may conclude:
- [conclusion]

### Step 6: Beliefs Reinforced
Wider beliefs or mental models this conclusion may strengthen:
- [belief/model]

### Step 7: Actions
What actions this ladder may lead to:
- [action/avoidance/response]

### Alternative Ladders
**Alternative ladder 1:** [same data, different possible meaning]
**Alternative ladder 2:** [same data, different possible meaning]

### Evidence-Seeking Questions
- What did I actually observe?
- What did I not observe?
- What else could this mean?
- What could I ask safely and respectfully?
- What evidence would change my interpretation?

### Dialogue Language
- "The story I'm telling myself is..."
- "What I noticed was..."
- "I may be missing something. Can you help me understand...?"
- "Another possibility is..."

Self-check: Do not invalidate emotion. Do not present alternatives as truth. Keep safety and dignity central.

Common Pitfalls

  • Using the ladder to dismiss emotion. Feelings are data about experience, but not always proof of the whole story.
  • Over-intellectualising harm. If harm occurred, do not use alternative ladders to excuse it.
  • Skipping observable data. Start with what can be seen/heard/read.
  • Assuming one correct interpretation. The goal is better inquiry, not forced consensus.

Known Limitations

  • Does not determine what actually happened. The ladder is a reflective tool, not an investigative one. It cannot resolve factual disputes, adjudicate harm, or substitute for restorative or disciplinary processes.
  • Not appropriate immediately after significant harm. Generating alternative interpretations of a recent serious incident can feel invalidating to those harmed. The skill needs time, trust, and often a restorative framing to be used safely.
  • Power asymmetry risk. When the people involved hold significantly different power (e.g. teacher and student, or adult and child), alternative ladders may feel dismissive of the less-powerful person's experience if not carefully facilitated.
  • Culturally bounded. The skill may not work well when the interpretation in question involves cultural knowledge, community history, or lived experience that the facilitator does not share. External cultural expertise may be required.

Verification Checklist

  • [ ] Observable data is separated from interpretation.
  • [ ] Assumptions are named tentatively.
  • [ ] At least two alternative ladders are included.
  • [ ] Dialogue language is safe and age-appropriate.
  • [ ] The output does not excuse harm or force reconciliation.

Other skills for the same job

different authors, same section of the catalogue
Skill Creator
by anthropics
vendor ×10

Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.

56k tokens scripts
Geo Database
by christophacham
×4

Access NCBI GEO for gene expression/genomics data. Search/download microarray and RNA-seq datasets (GSE, GSM, GPL), retrieve SOFT/Matrix files, for transcriptomics and expression analysis.

12k tokens
Pymc Bayesian Modeling
by christophacham
×4

Bayesian modeling with PyMC. Build hierarchical models, MCMC (NUTS), variational inference, LOO/WAIC comparison, posterior checks, for probabilistic programming and inference.

24k tokens scripts
Pymoo
by christophacham
×4

Multi-objective optimization framework. NSGA-II, NSGA-III, MOEA/D, Pareto fronts, constraint handling, benchmarks (ZDT, DTLZ), for engineering design and optimization problems.

19k tokens scripts
Statsmodels
by ComeOnOliver
×4

Statistical modeling toolkit. OLS, GLM, logistic, ARIMA, time series, hypothesis tests, diagnostics, AIC/BIC, for rigorous statistical inference and econometric analysis.

41k tokens
Add Uint Support
by pytorch
vendor ×3

Add unsigned integer (uint) type support to PyTorch operators by updating AT_DISPATCH macros. Use when adding support for uint16, uint32, uint64 types to operators, kernels, or when user mentions enabling unsigned types, barebones unsigned types, or uint support.

2k tokens
At Dispatch V2
by pytorch
vendor ×3

Convert PyTorch AT_DISPATCH macros to AT_DISPATCH_V2 format in ATen C++ code. Use when porting AT_DISPATCH_ALL_TYPES_AND*, AT_DISPATCH_FLOATING_TYPES*, or other dispatch macros to the new v2 API. For ATen kernel files, CUDA kernels, and native operator implementations.

2k tokens
Docstring
by pytorch
vendor ×3

Write docstrings for PyTorch functions and methods following PyTorch conventions. Use when writing or updating docstrings in PyTorch code.

3k tokens

How to use it

Copy the folder

Take garethmanning/ladder-of-inference-reflection from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.