Agent skill

thinking-leverage-points

Identify where small changes can have large effects using Donella Meadows' hierarchy of system intervention points. Use for strategic decisions, system optimization, and choosing where to focus engineering effort.

majiayu000534★ · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill thinking-leverage-points --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 12 KB
Bundled scripts: none
Path: skills/analysis/thinking-leverage-points/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Leverage Points ## Overview Donella Meadows' "Places to Intervene in a System" provides a hierarchy of intervention points ranked by their power to change system behavior. Most effort goes into low-leverage interventions (parameters, buffers) when high-leverage points (goals, paradigms) offer transformational change with less force. **Core Principle:** The higher in the hierarchy, the more leverage—but also the more resistance. Find the highest leverage point you can actually move. ## When to Use - Choosing where to focus engineering effort - Prioritizing system improvements - Organizational change initiatives - Architecture evolution decisions - Process optimization - Resource allocation - When incremental changes aren't working Decision flow: ``` Want to change system behavior? → Have you tried high-leverage interventions? → no → START HIGHER → Are you stuck at low leverage? → yes → MOVE UP THE HIERARCHY → Is change not sticking? → yes → LOOK FOR BALANCING LOOPS ``` ## The 12 Leverage Points (Low to High) ### Level 12: Constants and Parameters (LOWEST LEVERAGE) **What:** Numbers—budgets, rates, thresholds, timeouts **Examples:** - Adjusting cache TTL - Changing retry counts - M

What's inside
Steps it walks through
  1. Overview
  2. When to Use
  3. The 12 Leverage Points (Low to High)
  4. Level 12: Constants and Parameters (LOWEST LEVERAGE)
  5. Level 11: Buffer Sizes
  6. Level 10: Stock-and-Flow Structures
  7. Level 9: Delays
  8. Level 8: Balancing Feedback Loops
  9. Level 7: Reinforcing Feedback Loops
  10. Level 6: Information Flows
  11. Level 5: System Rules
  12. Level 4: Self-Organization
  13. Level 3: System Goals
  14. Level 2: Paradigm (Mindset)
Ships with 1 file
  • metadata.json
More from claude-skill-registry
All skills →
About this skill
What does the thinking-leverage-points skill do?

Identify where small changes can have large effects using Donella Meadows' hierarchy of system intervention points. Use for strategic decisions, system optimization, and choosing where to focus engineering effort.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill thinking-leverage-points --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going