Systems Thinking Leverage

Finds high-leverage intervention points in complex systems by mapping feedback loops, identifying system archetypes (fixes that fail, shifting the burden, tragedy of the commons, limits to growth), and ranking interventions by Meadows' leverage hierarchy. Use when problems involve interconnected components with feedback loops, delays, or emergent behavior; when past solutions failed or caused unintended consequences; when identifying where to push for maximum effect; or when user mentions systems thinking, leverage points, feedback loops, causal loop diagrams, stocks and flows, or complex syst

200 stars 25 forksFrontend & Design Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add lyndonkl/claude

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add lyndonkl/claude --skill systems-thinking-leverage
Manual install
git clone --depth 1 https://github.com/lyndonkl/claude.git /tmp/claude
mkdir -p ~/.claude/skills
cp -r /tmp/claude/skills/systems-thinking-leverage ~/.claude/skills/systems-thinking-leverage

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Systems Thinking & Leverage Points

## Workflow

Copy this checklist and track your progress:

```
Systems Thinking & Leverage Progress:
- [ ] Step 1: Define system and problem
- [ ] Step 2: Map system structure
- [ ] Step 3: Identify leverage points
- [ ] Step 4: Validate and test interventions
- [ ] Step 5: Design high-leverage strategy
```

**Step 1: Define system and problem**

Clarify system boundaries (what's in/out of system), key variables (stocks that accumulate, flows that change them), and problem symptom vs. underlying pattern. Use [System Definition](#system-definition) section below.

**Step 2: Map system structure**

For simple cases → Use [resources/template.md](resources/template.md) for quick causal loop diagram and stock-flow identification. For complex cases → Study [resources/methodology.md](resources/methodology.md) for system archetypes, multi-loop analysis, and time delays.

**Step 3: Identify leverage points**

Apply Meadows' leverage hierarchy (parameters < buffers < structure < delays < balancing loops < reinforcing loops < information < rules < self-organization < goals < paradigms). See [Leverage Points Analysis](#leverage-points-analysis) below and [resources/methodology.md](resources/methodology.md) for techniques.

**Step 4: Validate and test interventions**
Read the full skill on GitHub

Details

Skill name
systems-thinking-leverage
Path
skills/systems-thinking-leverage/SKILL.md
Repo updated
1 September 2026

FAQ

What does the Systems Thinking Leverage skill do?

Finds high-leverage intervention points in complex systems by mapping feedback loops, identifying system archetypes (fixes that fail, shifting the burden, tragedy of the commons, limits to growth), and ranking interventions by Meadows' leverage hierarchy. Use when problems involve interconnected components with feedback loops, delays, or emergent behavior; when past solutions failed or caused unintended consequences; when identifying where to push for maximum effect; or when user mentions systems thinking, leverage points, feedback loops, causal loop diagrams, stocks and flows, or complex syst

How do I install the Systems Thinking Leverage 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 Systems Thinking Leverage popular?

It lives in lyndonkl/claude, which has 200 GitHub stars and 25 forks.

Related skills

Abstraction Concrete Examples

200

lyndonkl/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.

Testing & QA25

Academic Letter Architect

200

lyndonkl/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.

Research & Science25

Adr Architecture

200

lyndonkl/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.

Software Development25

Wc Ownership Meta

200

lyndonkl/claude

Models the FIFA World Cup Fantasy field — effective ownership, the template set, the differential list, and the rank-protect-vs-gain leverage math — so the system reasons about "what will most managers do?" rather than raw points. Computes effective ownership EO = field_ownership% x (1 + captaincy_share), classifies every owned/missed player into the three regimes (own high-EO haul = hold station, MISS high-EO haul = drop hard, own low-EO haul = leap the field), builds the template set and differential list, flags where the field is over-concentrated (fade ops) and under-reacting (get-there-fi

Frontend & Design25

Synthesis Application

200

lyndonkl/claude

Domain-neutral methodology for evaluating completeness and logical soundness of an extracted set of components, then transforming them into actionable guidance. Runs the "is it true / is it complete / what of it" critical evaluation pass before any final artifact is built. Checks for completeness gaps, logical consistency, contradictions, and practical applicability. Reusable across any extraction workflow - skill creation (evaluating extracted components before building SKILL.md), paper extraction (evaluating Pass 2 extraction notes before deep reading), report writing (evaluating gathered ev

Frontend & Design25

Worked Example Walkthrough

200

lyndonkl/claude

Produces step-by-step computational walkthroughs of vector and matrix operations as a sequence of numbered "frames", showing the explicit state at each step. The text-equivalent of a 3Blue1Brown animation — each frame shows what changed and why, so the learner can re-trace the operation by hand. Use when the learner needs to *see* a computation unfold (eigenvalue computation, attention with 3 tokens, gradient descent step, SVD on a 2×2, layer norm on a 3-vector, softmax of a small input), when an explanation has been given but the learner needs to ground it in a worked example, or when introdu

Frontend & Design25

Browse the most popular Claude skills, all frontend & design skills, or write your own with the skills generator.