Ladder of Abstraction
Moves prose deliberately between the concrete and the abstract and stops it stranding in the middle rung where bureaucratic prose lives. Tags every paragraph R1 (named particulars) to R4 (meaning), enforces run rules, detects the middle-rung trap, repairs it by climbing down to a real particular rather than simplifying vocabulary, gates the top rung with a counter-sentence test, and closes with an A-frame descent. Use when a draft reads as dense, vague, or jargon-heavy, when a readability score fails, when a conclusion feels grandiose or unearned, when technical material will not land for a ge
Install
/plugin marketplace add lyndonkl/claudeThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add lyndonkl/claude --skill ladder-of-abstractiongit clone --depth 1 https://github.com/lyndonkl/claude.git /tmp/claude
mkdir -p ~/.claude/skills
cp -r /tmp/claude/skills/ladder-of-abstraction ~/.claude/skills/ladder-of-abstractionPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Ladder Of Abstraction ## Table of Contents - [Core Principles](#core-principles) - [Workflow](#workflow) - [The Four Rungs](#the-four-rungs) - [Run Rules and Violations](#run-rules-and-violations) - [Readability Routing](#readability-routing) - [Guardrails](#guardrails) - [Quick Reference](#quick-reference) **Related skills:** Use `readability-check` for the actual scoring pass (this skill diagnoses what a failing score means), `writing-structure-planner` for section order and shape, `hedge-detector` when repairs threaten epistemic hedges, `abstraction-concrete-examples` for building explanatory ladders from scratch rather than auditing a draft, `systemic-protagonist` for the full agency-repair ledger when the subject is a system. ## Core Principles 1. **The middle rung is a transit lane, not a parking space**: prose the reader can neither see nor understand is usually stuck halfway up, not too technical. 2. **Climb down, never simplify**: the only real fix for an abstract paragraph is one particular instance from the material. Swapping jargon for plainer jargon changes the reading score and not the comprehensibility. 3. **No particular, no paragraph**: if the material contains no instance, that is a reporting gap to log, not a detail to invent. 4. **The honest ceiling is set by the material**: if your top-rung claim could be attached to any story in the domain, it is generic. A piece is allowed to mean something small.
Details
- Skill name
ladder-of-abstraction- Repository
- lyndonkl/claude
- Path
skills/ladder-of-abstraction/SKILL.md- Repo updated
- 1 September 2026
FAQ
What does the Ladder of Abstraction skill do?
Moves prose deliberately between the concrete and the abstract and stops it stranding in the middle rung where bureaucratic prose lives. Tags every paragraph R1 (named particulars) to R4 (meaning), enforces run rules, detects the middle-rung trap, repairs it by climbing down to a real particular rather than simplifying vocabulary, gates the top rung with a counter-sentence test, and closes with an A-frame descent. Use when a draft reads as dense, vague, or jargon-heavy, when a readability score fails, when a conclusion feels grandiose or unearned, when technical material will not land for a ge
How do I install the Ladder of Abstraction skill?
Claude Code plugin: /plugin marketplace add lyndonkl/claude. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Ladder of Abstraction popular?
It lives in lyndonkl/claude, which has 200 GitHub stars and 25 forks.
Related skills
Abstraction Concrete Examples
200lyndonkl/claude
Builds structured abstraction ladders that translate high-level principles into concrete, actionable examples across 3-5 levels. Bridges communication gaps, reveals hidden assumptions, and tests whether abstract ideas work in practice. Use when explaining concepts at different expertise levels, moving between abstract principles and concrete implementation, identifying edge cases by testing ideas against scenarios, designing layered documentation, decomposing complex problems into actionable steps, or bridging strategy-execution gaps.
Academic Letter Architect
200lyndonkl/claude
Guides the creation of evidence-based academic recommendation letters, reference letters, and award nominations that combine concrete examples, meaningful comparisons, and genuine enthusiasm. Use when writing recommendation letters for students, postdocs, or colleagues, or when user mentions recommendation letter, reference, nomination, letter of support, endorsement, or needs help with strong advocacy and comparative statements.
Adr Architecture
200lyndonkl/claude
Documents significant architectural and technical decisions with full context, alternatives considered, trade-offs analyzed, and consequences understood. Creates a decision trail that helps teams understand why decisions were made. Use when choosing between technology options, making infrastructure decisions, establishing standards, migrating systems, or when user mentions ADR, architecture decision, technical decision record, or decision documentation.
Mcphee Structure Derivation
200lyndonkl/claude
Derives a document's structure out of its own corpus instead of picking one off a menu, using John McPhee's coding-and-sorting procedure - cold read, short topic codes one per card, a strict chronology sort run against a strict theme sort, a logged list of every disagreement resolved toward chronology, candidate juxtapositions gated by a state-and-footnote test, a named shape, and an invisibility test. Use when you hold researched material and have no structure yet, when a draft has turned into concept-named sections full of time-scrambled evidence, when deciding whether a flashback is earned,
Hypotheticals Counterfactuals
200lyndonkl/claude
Applies "what if" thinking to explore alternative scenarios, test assumptions, understand causal relationships, and prepare for uncertainty. Guides through counterfactual reasoning, scenario exploration, pre-mortem analysis, and stress testing decisions against alternative futures. Use when exploring alternative scenarios, testing assumptions through "what if" questions, understanding causal relationships, conducting pre-mortem analysis, stress testing decisions, or when user mentions counterfactuals, hypothetical scenarios, thought experiments, alternative futures, what-if analysis, or needs
Narrative Fallacy Guard
200lyndonkl/claude
Stops a true set of facts from being assembled into a false story. Runs the retrospective slot audit, the outcome-blind rewrite (flip test, separation test), the inevitability audit with its overshoot check, the survivorship graveyard pass, the counterfactual admissibility gate, and the expensive proportion and omission audits. Every check labels and discloses; none deletes. Use when drafting or reviewing history, post-mortems, biography, market or protocol narratives, research writeups, or any account written after the outcome was known, or when user mentions hindsight bias, narrative fallacy
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.