Agent skill

Systems Thinking Practitioner

by FerroxLabs in FerroxLabs/wayland

Applied systems thinking guide covering feedback loops, leverage points, causal loop diagrams, system archetypes, mental models, stocks and flows, and practical tools for understanding and…

Apache-2.0Auto-check passedDevelopment

Install Systems Thinking Practitioner

skills CLI
$ npx skills add FerroxLabs/wayland --skill systems-thinking-practitioner -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install FerroxLabs/wayland systems-thinking-practitioner --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/FerroxLabs/wayland.git skills-src && mkdir -p .claude/skills && cp -r skills-src/src/process/resources/skills-library/bodies/skills/productivity/systems-thinking-practitioner .claude/skills/systems-thinking-practitioner && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
systems-thinking-practitioner
GitHub stars
608
Token cost
~3.1k tokens
SKILL.md length
414 words
Files
1
Skills in repo
1,194
Repo updated
First seen
Licence
Apache-2.0

At a glance

Applied systems thinking guide covering feedback loops, leverage points, causal loop diagrams, system archetypes, mental models, stocks and flows, and practical tools for understanding and…

  • Works in 6 steps: What system or problem are you trying to… → What behavior are you observing that… → What interventions have been tried? (And… → …
  • The user asks about systems thinking practitioner
  • SKILL.md covers When to Use, Questions to Ask First, Core Concepts and Building Causal Loop Diagrams, plus 7 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Systems Thinking Practitioner is an agent skill from FerroxLabs/wayland. Applied systems thinking guide covering feedback loops, leverage points, causal loop diagrams, system archetypes, mental models, stocks and flows, and practical tools for understanding and intervening in complex systems. Use when the user asks about systems thinking practitioner, related techniques, best practices, or needs guidance in this domain. Do NOT use when the request is outside the scope of systems thinking practitioner or requires a different specialized skill.

Its SKILL.md is about 3.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Diagrams. The repository describes itself as: Wayland - The AI Agent That Perceives. Reasons. Acts. Evolves. The licence is Apache-2.0.

When your agent uses it

  • The user asks about systems thinking practitioner
  • Related techniques
  • Needs guidance in this domain
  • The request is outside the scope of systems thinking practitioner

Example prompts

  • “/systems-thinking-practitioner”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. What system or problem are you trying to understand?
  2. What behavior are you observing that concerns you? (Growth, decline, oscillation, stagnation)
  3. What interventions have been tried? (And why they may not have worked)
  4. Who are the key actors in this system?
  5. What time horizon are you considering? (Weeks, months, years, decades)
  6. What data do you have about the system's behavior over time?

What it can do on your machine

Read from SKILL.md and the folder at commit 4c030c7. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are template).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Systems Thinking Practitioner loads about 3.1k tokens when it runs. Until then it costs about 126 tokens; SKILL.md has 414 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~126
When it runs · the whole SKILL.md, loaded when a task matches
~3.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from FerroxLabs/wayland at commit 4c030c7, republished under its Apache-2.0 licence (© FerroxLabs). 414 words, ~3,146 tokens.

Download SKILL.mdSave it as .claude/skills/systems-thinking-practitioner/SKILL.md (or your agent's skills folder).
name
systems-thinking-practitioner
description
Applied systems thinking guide covering feedback loops, leverage points, causal loop diagrams, system archetypes, mental models, stocks and flows, and practical tools for understanding and intervening in complex systems. Use when the user asks about systems thinking practitioner, related techniques, best practices, or needs guidance in this domain. Do NOT use when the request is outside the scope of systems thinking practitioner or requires a different specialized skill.
license
Apache-2.0
metadata.author
foundry-skills
metadata.version
1.0.0
metadata.tags
time-management frameworks budgeting guide step-by-step cloud analysis planning
metadata.category
productivity
metadata.subcategory
methodology-frameworks
metadata.disclaimer
none
metadata.difficulty
intermediate

Systems Thinking Practitioner

You are a systems thinking coach who helps people see beyond linear cause-and-effect to understand the circular, interconnected nature of complex problems. You draw from the work of Donella Meadows, Peter Senge, Jay Forrester, and others to make systems thinking practical and applicable to business, organizational, and personal challenges.

When to Use

Use this skill when:

  • User asks about systems thinking practitioner techniques or best practices
  • User needs guidance on systems thinking practitioner concepts
  • User wants to implement or improve their approach to systems thinking practitioner

Do NOT use when:

  • The request falls outside the scope of systems thinking practitioner
  • User needs a different specialized skill for their specific situation
  • The topic requires professional consultation beyond general guidance

Questions to Ask First

  1. What system or problem are you trying to understand?
  2. What behavior are you observing that concerns you? (Growth, decline, oscillation, stagnation)
  3. What interventions have been tried? (And why they may not have worked)
  4. Who are the key actors in this system?
  5. What time horizon are you considering? (Weeks, months, years, decades)
  6. What data do you have about the system's behavior over time?

Core Concepts

Feedback Loops
REINFORCING LOOPS (R): Amplify change in one direction
- Growth: More customers -> more revenue -> more marketing -> more customers
- Decline: Employee turnover -> more workload -> more burnout -> more turnover
- These loops drive exponential growth OR collapse
- Question to ask: "What is the engine driving this growth/decline?"

BALANCING LOOPS (B): Resist change, seek equilibrium
- Thermostat: Temperature rises -> heater turns off -> temperature falls
- Market: Price rises -> demand falls -> price falls
- These loops drive toward stability or targets
- Question to ask: "What is this system trying to maintain?"

DELAYS: Time gaps between cause and effect
- Construction: Decide to build -> years before capacity available
- Hiring: Recruit -> months before new hire is productive
- Delays cause oscillation (overshoot and undershoot)
- Question to ask: "How long before we see the effect of this action?"
Stocks and Flows
STOCKS: Accumulations (things you can count at a point in time)
Examples: inventory, cash balance, employee count, customer base,
          knowledge, trust, technical debt, pollution levels

FLOWS: Rates of change (things you measure over time)
Inflows:  hiring rate, revenue rate, learning rate
Outflows: attrition rate, spending rate, depreciation rate

THE BATHTUB ANALOGY:
Stock = water level in the bathtub
Inflow = faucet (adds water)
Outflow = drain (removes water)
Level changes = inflow rate minus outflow rate

KEY INSIGHT: Stocks change slowly even when flows change quickly.
This is why organizations feel sluggish to change.
Even if you stop all hiring today, your workforce stock decreases
only at the attrition rate.
Leverage Points
MEADOWS' LEVERAGE POINTS (from least to most effective):

12. Numbers (subsidies, taxes, standards) - least leverage
11. Buffer sizes (stabilizing stocks)
10. Stock-and-flow structure (physical systems)
9.  Delays (in feedback loops)
8.  Balancing feedback loops (strength relative to impacts)
7.  Reinforcing feedback loops (driving growth or collapse)
6.  Information flows (who has access to what)
5.  Rules (incentives, constraints, punishments)
4.  Self-organization (ability to change structure)
3.  Goals (purpose of the system)
2.  Paradigm (mindset behind the system)
1.  Transcending paradigms - most leverage

PRACTICAL APPLICATION:
Most interventions target level 12 (adjusting numbers).
The most effective interventions target levels 3-6.
Ask: "Am I pushing a parameter or changing the structure?"
System Archetypes
FIXES THAT FAIL:
Pattern: Quick fix addresses symptom -> side effect makes problem worse
Example: Overtime to meet deadlines -> burnout -> lower productivity -> more overtime
Solution: Address the root cause instead of the symptom

SHIFTING THE BURDEN:
Pattern: Symptomatic solution crowds out fundamental solution
Example: Painkillers for chronic back pain instead of addressing posture/core strength
Solution: Strengthen the fundamental solution while managing symptoms

LIMITS TO GROWTH:
Pattern: Reinforcing growth hits a constraint that slows/stops it
Example: Startup grows fast -> quality drops -> customer complaints -> growth stalls
Solution: Identify and address the constraint before it bites

TRAGEDY OF THE COMMONS:
Pattern: Individuals deplete shared resource for personal gain
Example: All teams requesting more cloud compute -> costs explode -> budget cuts for all
Solution: Regulate access, create visibility, align incentives with collective good

ESCALATION:
Pattern: Two parties each try to gain advantage, driving mutual escalation
Example: Price war between competitors -> both lose margin -> industry damaged
Solution: Negotiate, find alternative competition dimensions, or one party de-escalates

SUCCESS TO THE SUCCESSFUL:
Pattern: Winner gets more resources -> wins more -> gets more resources
Example: Top-performing team gets more budget -> outperforms further -> others starve
Solution: Equalize resource access or create separate arenas

Building Causal Loop Diagrams

STEP-BY-STEP PROCESS:

1. IDENTIFY THE PROBLEM BEHAVIOR:
   "What is the trend we are trying to understand?"
   Draw a behavior-over-time graph.

2. IDENTIFY KEY VARIABLES:
   List the 5-10 most important variables.
   Use nouns that can increase or decrease (not actions).
   Good: "Employee morale"  Bad: "Improve morale"

3. MAP CAUSAL CONNECTIONS:
   For each pair of related variables, draw an arrow.
   Label: + (same direction) or - (opposite direction)
   A +-> B: When A increases, B increases (and vice versa)
   A --> B: When A increases, B decreases (and vice versa)

4. IDENTIFY LOOPS:
   Trace closed paths. Count the negative (-) links.
   Even number of negatives (or zero) = Reinforcing (R)
   Odd number of negatives = Balancing (B)

5. IDENTIFY DELAYS:
   Mark any connections where the effect is significantly delayed.
   Use a double line or delay marker on the arrow.

6. TELL THE STORY:
   Walk through each loop in narrative form.
   "As X increases, this causes Y to increase, which in turn..."

NOTATION:
Variable A ---(+)---> Variable B  (same direction)
Variable A ---(-)---> Variable B  (opposite direction)
Variable A ===(+)===> Variable B  (same direction, with delay)

Practical Tools

The Iceberg Model
EVENTS (visible):
  "What just happened?"
  Example: "We missed the quarterly target."

PATTERNS (over time):
  "What trends have been occurring?"
  Example: "We have missed targets 3 of the last 4 quarters."

STRUCTURES (systemic):
  "What systems or relationships are creating these patterns?"
  Example: "Our incentive structure rewards individual deals over
  team collaboration, leading to sandbagging and uneven pipelines."

MENTAL MODELS (deepest):
  "What assumptions and beliefs are holding these structures in place?"
  Example: "Leadership believes competition between salespeople
  drives performance, so they resist collaborative models."

INTERVENTION STRATEGY:
- Events: react (necessary but not sufficient)
- Patterns: anticipate and adapt
- Structures: redesign for different outcomes
- Mental models: transform thinking (hardest but most powerful)
Systems Mapping Workshop Format
FACILITATION GUIDE (90 minutes):

SETUP (10 min):
- Define the focal question
- Agree on time horizon
- Establish ground rules (no blame, curiosity, all perspectives valid)

VARIABLE BRAINSTORM (15 min):
- Each person writes 3-5 key variables on sticky notes
- Post all notes, cluster similar ones
- Agree on 8-12 most important variables

CONNECTION MAPPING (30 min):
- Place variables on a large surface
- Draw arrows between connected variables
- Label each arrow + or -
- Identify and label loops (R or B)
- Mark significant delays

ANALYSIS (20 min):
- Which loops are dominant right now?
- Where are the delays causing problems?
- What archetype does this resemble?
- Where are the potential leverage points?

ACTION PLANNING (15 min):
- Identify 2-3 high-leverage interventions
- Consider unintended consequences of each
- Assign owners and next steps

Application to Common Business Problems

PROBLEM: High employee turnover
SYSTEMS PERSPECTIVE:
- Map the reinforcing loop: turnover -> workload -> burnout -> turnover
- Identify balancing loops: hiring, compensation, culture initiatives
- Look for delays: time to hire, time to onboard, culture change lag
- Find leverage: often in management quality, not compensation

PROBLEM: Product quality declining
SYSTEMS PERSPECTIVE:
- Map: pressure to ship -> shortcuts -> defects -> customer complaints
  -> more pressure to fix -> less time for new features -> more pressure
- Identify: technical debt as a stock (accumulates, hard to reduce)
- Find leverage: usually in development practices and capacity planning

PROBLEM: Strategy not being executed
SYSTEMS PERSPECTIVE:
- Map: strategic goals vs operational demands competing for attention
- Identify: shifting the burden from strategic investment to firefighting
- Find leverage: protect strategic time, separate operational and strategic work

Mental Models for Systems Thinkers

ESSENTIAL MENTAL MODELS:
1. Feedback thinking: Every action creates reactions in the system
2. Non-linearity: Small causes can have large effects (and vice versa)
3. Emergence: System behavior cannot be predicted from parts alone
4. Bounded rationality: Actors make locally rational decisions that
   may be globally suboptimal
5. Path dependence: History constrains current options
6. Requisite variety: Responses must match the complexity of challenges
Show full SKILL.md (187 more words)Show less

Process

  1. Gather information. Ask the user clarifying questions to understand their specific situation, goals, and constraints
  2. Analyze context. Review the information provided and identify key factors relevant to systems thinking practitioner
  3. Develop recommendations. Apply domain expertise to create actionable guidance tailored to the user's needs
  4. Present structured output. Deliver findings in the output format below with clear next steps
  5. Address follow-ups. Answer additional questions and refine recommendations based on feedback

Output Format

template
## Systems Thinking Practitioner Analysis

### Assessment
[Key findings and observations]

### Recommendations
1. [Primary recommendation]
2. [Secondary recommendation]
3. [Additional suggestions]

### Action Items
- [ ] [First action step]
- [ ] [Second action step]
- [ ] [Follow-up task]

Edge Cases

  • Incomplete information: Ask clarifying questions before proceeding with recommendations
  • Conflicting requirements: Prioritize the most critical constraint and note trade-offs
  • Out of scope requests: Redirect to appropriate specialized skill or professional resource
  • Beginner vs advanced: Adjust depth and terminology based on user's experience level

Example

Input: "Help me with systems thinking practitioner for my current situation"

Output:

Based on your situation, here is a structured approach to systems thinking practitioner:

  1. Assessment: Evaluate your current state and identify key areas for improvement
  2. Strategy: Develop a targeted plan based on best practices
  3. Implementation: Execute the plan with specific, measurable steps
  4. Review: Monitor progress and adjust as needed

© FerroxLabs, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in src/process/resources/skills-library/bodies/skills/productivity/systems-thinking-practitioner of FerroxLabs/wayland.

Open the folder on GitHubat commit 4c030c7

Compare with similar skills

Systems Thinking Practitioner next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Systems Thinking Practitioner compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Systems Thinking Practitioner this skillFerroxLabs/wayland608—~3.1kAutomated safety check: PassApache-2.0
JSON Canvasheyitsnoah/claudesidian2.6k18 repos~3.5kAutomated safety check: PassMIT
Archify Diagramstt-a1i/archify79k—~2.9kAutomated safety check: PassMIT
Diagram Designcathrynlavery/diagram-design44k1 repos~7.5kAutomated safety check: PassMIT
Fireworks Tech Graphtisfeng/Easydict15k1 repos~1.4kAutomated safety check: PassMIT
Excalidraw Diagramcoleam00/excalidraw-diagram-skill4.9k2 repos~6.1kAutomated safety check: PassNone

Similar skills

  • JSON Canvas

    heyitsnoah/claudesidian

    Create and edit JSON Canvas files (.canvas) with nodes, edges, groups, and connections.

    2.6k GitHub starsUsed in 18 repos~3.5k tokens
    DevelopmentAuto-check passed
  • Archify Diagrams

    tt-a1i/archify

    Creates interactive architecture, workflow, sequence, data-flow and lifecycle diagrams as standalone HTML with inline SVG, themes and image or video export.

    79k GitHub stars~2.9k tokensUpdated today
    DevelopmentAuto-check passed
  • Diagram Design

    cathrynlavery/diagram-design

    Creates branded diagrams, from architecture, flowchart and sequence to charts and maps, as self-contained HTML with inline SVG, with import from draw.io, Mermaid and Excalidraw.

    44k GitHub starsUsed in 1 repo~7.5k tokens
    DevelopmentAuto-check passed
  • Fireworks Tech Graph

    tisfeng/Easydict

    Create precise SVG technical diagrams, export PNG or offline HTML, and animate supported semantic SVGs to GIF.

    15k GitHub starsUsed in 1 repo~1.4k tokens
    DevelopmentAuto-check passed
  • Excalidraw Diagram

    coleam00/excalidraw-diagram-skill

    Create Excalidraw diagram JSON files that make visual arguments.

    4.9k GitHub starsUsed in 2 repos~6.1k tokens
    DevelopmentAuto-check passed
  • Draw.io Diagram Studio

    Agents365-ai/drawio-skill

    Creates and edits editable draw.io diagrams from descriptions, code, infrastructure files, SQL and API schemas, with sync, review, test and export tools.

    10k GitHub stars~2.4k tokensUpdated 5 days ago
    DevelopmentAuto-check: notes

More from FerroxLabs/wayland

All 1,194 skills in this repo
  • Star Office Helper

    FerroxLabs/wayland

    Install, start, connect, and troubleshoot visualization companion projects for Aion/OpenClaw, with Star-Office-UI as the default recommendation.

    608 GitHub stars~2.2k tokensUpdated yesterday
    Auto-check: notes
  • Openclaw Setup

    FerroxLabs/wayland

    OpenClaw usage expert: Helps you install, deploy, configure, and use OpenClaw personal AI assistant.

    608 GitHub stars~1.9k tokensUpdated yesterday
    Auto-check passed
  • Tvcontrol Setup

    FerroxLabs/wayland

    Set up TVControl end to end: install the connector, start TradingView Desktop with its control port open, load a watchlist export, add the indicators they use, and leave a working chart.

    608 GitHub stars~5.7k tokensUpdated yesterday
    Auto-check passed
  • Ab Testing Specialist

    FerroxLabs/wayland

    End-to-end guide for designing, running, and analyzing A/B tests including experiment design, statistical significance, sample size calculation, common pitfalls, and advanced testing patterns.

    608 GitHub stars~3.7k tokensUpdated yesterday
    Auto-check passed
  • Academic Writer

    FerroxLabs/wayland

    Complete academic writing guide covering thesis and dissertation structure, journal article format using IMRaD, literature review methodology, citation management, the peer review process, and…

    608 GitHub stars~4.5k tokensUpdated yesterday
    Auto-check passed
  • Accessibility Auditor

    FerroxLabs/wayland

    Web accessibility expertise covering WCAG 2.2 conformance, audit methodology, ARIA patterns, keyboard navigation, screen reader testing, focus management, form accessibility, and automated vs manual…

    608 GitHub stars~4.1k tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Systems Thinking Practitioner

What does Systems Thinking Practitioner do?

Applied systems thinking guide covering feedback loops, leverage points, causal loop diagrams, system archetypes, mental models, stocks and flows, and practical tools for understanding and…. Systems Thinking Practitioner is an agent skill from FerroxLabs/wayland. Applied systems thinking guide covering feedback loops, leverage points, causal loop diagrams, system archetypes, mental models, stocks and flows, and practical tools for understanding and intervening in complex systems.

When should I use Systems Thinking Practitioner?

Systems Thinking Practitioner fits situations like: the user asks about systems thinking practitioner; related techniques; needs guidance in this domain; the request is outside the scope of systems thinking practitioner.

How do I install Systems Thinking Practitioner in Claude Code?

Run `npx skills add FerroxLabs/wayland --skill systems-thinking-practitioner -a claude-code`. Or copy the skill folder (src/process/resources/skills-library/bodies/skills/productivity/systems-thinking-practitioner in FerroxLabs/wayland) into .claude/skills/systems-thinking-practitioner in your project. Claude Code loads it when a task matches its description.

How do I install Systems Thinking Practitioner in Codex?

Run `npx skills add FerroxLabs/wayland --skill systems-thinking-practitioner -a codex`. Or copy the skill folder (src/process/resources/skills-library/bodies/skills/productivity/systems-thinking-practitioner in FerroxLabs/wayland) into .agents/skills/systems-thinking-practitioner in your project. Codex loads it when a task matches its description.

Can I use Systems Thinking Practitioner in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add FerroxLabs/wayland --skill systems-thinking-practitioner -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/systems-thinking-practitioner, .gemini/skills/systems-thinking-practitioner, .github/skills/systems-thinking-practitioner and .opencode/skills/systems-thinking-practitioner in your project.

What does Systems Thinking Practitioner need to run?

SKILL.md names no scripts, command-line tools or credentials: Systems Thinking Practitioner is instructions for the agent only.

Does Systems Thinking Practitioner access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Systems Thinking Practitioner safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Systems Thinking Practitioner use?

Systems Thinking Practitioner is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Systems Thinking Practitioner use?

About 3.1k tokens (SKILL.md is roughly 13k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Systems Thinking Practitioner?

Skills that share tags, products or a category with Systems Thinking Practitioner: JSON Canvas (heyitsnoah/claudesidian, 2.6k stars), Archify Diagrams (tt-a1i/archify, 79k stars), Diagram Design (cathrynlavery/diagram-design, 44k stars) and Fireworks Tech Graph (tisfeng/Easydict, 15k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Systems Thinking Practitioner?

FerroxLabs (a GitHub user) maintains it in FerroxLabs/wayland, which has 608 GitHub stars. The repository holds 1,194 skills in this directory. The repository was last updated on October 6, 2026.

Source: FerroxLabs/wayland on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.