Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Systems Leverage Analysis

ASecurity

Finds where small interventions produce large, lasting change using Donella Meadows' leverage point hierarchy. Use when asked 'where should we intervene', 'highest leverage', 'what actually changes this system', or 'find the lever'.

19 stars
0 votes
0 copies
1 views
Added 9/19/2026
ai-agentsgo

Security Analysis

A100/100

Scanned 9/19/2026

Install to Claude Code

$npx -y skills add rondoflow/rondoflow --skill systems-leverage-analysis --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Systems Leverage Analysis?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Systems Leverage Analysis
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/rondoflow-systems-leverage-analysis/badge)](https://www.skillsdirectory.com/skills/rondoflow-systems-leverage-analysis)

More formats (shields.io, HTML) on the badges page.

Download with Pro
Files
SKILL.md
---
name: systems-leverage-analysis
description: "Finds where small interventions produce large, lasting change using Donella Meadows' leverage point hierarchy. Use when asked 'where should we intervene', 'highest leverage', 'what actually changes this system', or 'find the lever'."
---

# Systems Leverage Analysis

Most interventions target low-leverage parameters — adjusting numbers, tweaking rates — when high-leverage structural points are available and being ignored. Donella Meadows identified 12 places to intervene in a system, ranging from parameters (nearly powerless) to paradigm (most powerful). The reason high-leverage points go unused is that they face the highest resistance; understanding this is part of the analysis.

---

## Your Process

**Step 1: List Candidate Interventions**
Gather all interventions currently being considered or tried. Include past attempts that failed.

**Framing check:** Confirm the specific system and the interventions in focus before continuing. State what you've identified — the system being analysed and the intervention set you're working with — in one sentence, then use `AskUserQuestion`:
- **Question:** "I'm reading this as: [your one-sentence framing of the system and the interventions being examined]. Is that right?"
- **Header:** "Framing"
- **Options:**
  - **Yes — proceed** — framing is correct
  - **Adjust** — one element is off; user will correct it before you continue
  - **Reframe** — different situation than read; incorporate the correction before proceeding

**Step 2: Classify by Meadows Hierarchy**
Map each intervention to its leverage level:
- **Low:** numbers/parameters, buffer sizes, flow rates
- **Medium:** feedback loop strength, information flows, rules of the system
- **High:** goals of the system, system structure, paradigm (the beliefs that create the system)

**Step 3: Identify the Default Level**
What level is typically targeted — and why? Understand the political, cognitive, or practical reasons low-leverage points get chosen.

**Step 4: Surface Ignored High-Leverage Points**
**Before narrowing:** Show the complete classified set of interventions from Step 2 to the user first. Use `AskUserQuestion`:
- **Question:** "I've identified [N] interventions across the leverage hierarchy. Before I select the highest-leverage options to focus on, are there any you'd flag as especially important, or any I've missed?"
- **Header:** "Prioritise"
- **Options:**
  - **Proceed with your selection** — the set looks right
  - **Flag one** — user will name a specific intervention to include
  - **Add a missing one** — user will describe it

What higher-leverage interventions exist that are not being tried? Trace why they are being avoided (too costly, politically threatening, requires belief change, long time horizon).

**Step 5: Assess Feasibility**
High-leverage points often face disproportionate resistance. For each high-leverage option: what would be required to act on it? Is it feasible given current constraints?

---

## Human Check-in

Before proceeding, use the `AskUserQuestion` tool. State your interpretation of the situation in 1–2 sentences — what is being analyzed and what the core question is — then ask:

- **Question:** "My read: [your 1–2 sentence interpretation]. How do you want to proceed?"
- **Header:** "Scope"
- **Options:**
  - **Full analysis** — Complete all steps, reasoning shown throughout
  - **Key findings only** — Bottom-line output, skip step-by-step detail
  - **Highest leverage point only** — Single best intervention, skip lower-leverage options
  - **Reframe** — The read is off; correct it and the analysis will follow the corrected framing

Proceed based on their selection. If the user reframes, incorporate the correction before running any analysis.

## Output Format

**Intervention Table**

| Intervention | Leverage Level | Leverage Type | Feasibility | Resistance Source |
|-------------|---------------|--------------|-------------|-------------------|
| | | | | |

**Default Level Being Targeted:** [level + reason]

**Highest-Leverage Feasible Point:** [intervention + why it's higher leverage + what unlocks it]

**Ignored High-Leverage Options:** [what they are + why they're being avoided]

---

## Notes

High-leverage points are often counterintuitive — pushing harder in the obvious direction can make things worse. Identify any points where the intuitive intervention is actually negative leverage.

---

## What's Next

After delivering this output, use `AskUserQuestion` to offer the next move:

- **Question:** "Leverage points identified. What's next?"
- **Header:** "Next"
- **Options:**
  - `/strategy-positioning` — Use leverage points for strategic positioning
  - `/resource-allocation-analysis` — Allocate resources to the highest-leverage points
  - `/decision-premortem-analysis` — Stress-test the assumptions behind leverage estimates
  - **Done** — Wrap up and synthesise what we have so far

Attribution

rondoflowrondoflow
View sourceMore from rondoflow →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Ultra-compressed communication mode that cuts output tokens while keeping technical accuracy. Levels: lite, full, ultra and the wenyan variants. Use for /caveman, "caveman mode", "talk like caveman", "be brief" or "less tokens".

1074701 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

693621 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3351 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

691 votes

math-skill

A comprehensive mathematical reasoning skill for AI assistants — handles arithmetic to research-level problems with rigorous step-by-step reasoning, systematic verification, and transparent uncertainty handling

381 votes
View all in ai-agents →