JSON Canvas
heyitsnoah/claudesidian
Create and edit JSON Canvas files (.canvas) with nodes, edges, groups, and connections.
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…
$ npx skills add FerroxLabs/wayland --skill systems-thinking-practitioner -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install FerroxLabs/wayland systems-thinking-practitioner --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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-srcUse ~/.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/
Install the "systems-thinking-practitioner" agent skill from https://github.com/FerroxLabs/wayland/tree/main/src/process/resources/skills-library/bodies/skills/productivity/systems-thinking-practitioner into .claude/skills/systems-thinking-practitioner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "systems-thinking-practitioner", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/FerroxLabs/wayland/tree/main/src/process/resources/skills-library/bodies/skills/productivity/systems-thinking-practitionerType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add FerroxLabs/wayland --skill systems-thinking-practitioner -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install FerroxLabs/wayland systems-thinking-practitioner --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/FerroxLabs/wayland.git skills-src && mkdir -p .agents/skills && cp -r skills-src/src/process/resources/skills-library/bodies/skills/productivity/systems-thinking-practitioner .agents/skills/systems-thinking-practitioner && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "systems-thinking-practitioner" agent skill from https://github.com/FerroxLabs/wayland/tree/main/src/process/resources/skills-library/bodies/skills/productivity/systems-thinking-practitioner into .agents/skills/systems-thinking-practitioner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "systems-thinking-practitioner", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add FerroxLabs/wayland --skill systems-thinking-practitioner -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install FerroxLabs/wayland systems-thinking-practitioner --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/FerroxLabs/wayland.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/src/process/resources/skills-library/bodies/skills/productivity/systems-thinking-practitioner .cursor/skills/systems-thinking-practitioner && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "systems-thinking-practitioner" agent skill from https://github.com/FerroxLabs/wayland/tree/main/src/process/resources/skills-library/bodies/skills/productivity/systems-thinking-practitioner into .cursor/skills/systems-thinking-practitioner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "systems-thinking-practitioner", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/FerroxLabs/wayland.git --path src/process/resources/skills-library/bodies/skills/productivity/systems-thinking-practitioner--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add FerroxLabs/wayland --skill systems-thinking-practitioner -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install FerroxLabs/wayland systems-thinking-practitioner --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/FerroxLabs/wayland.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/src/process/resources/skills-library/bodies/skills/productivity/systems-thinking-practitioner .gemini/skills/systems-thinking-practitioner && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "systems-thinking-practitioner" agent skill from https://github.com/FerroxLabs/wayland/tree/main/src/process/resources/skills-library/bodies/skills/productivity/systems-thinking-practitioner into .gemini/skills/systems-thinking-practitioner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "systems-thinking-practitioner", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install FerroxLabs/wayland systems-thinking-practitionerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add FerroxLabs/wayland --skill systems-thinking-practitioner -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/FerroxLabs/wayland.git skills-src && mkdir -p .github/skills && cp -r skills-src/src/process/resources/skills-library/bodies/skills/productivity/systems-thinking-practitioner .github/skills/systems-thinking-practitioner && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "systems-thinking-practitioner" agent skill from https://github.com/FerroxLabs/wayland/tree/main/src/process/resources/skills-library/bodies/skills/productivity/systems-thinking-practitioner into .github/skills/systems-thinking-practitioner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "systems-thinking-practitioner", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add FerroxLabs/wayland --skill systems-thinking-practitioner -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install FerroxLabs/wayland systems-thinking-practitioner --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/FerroxLabs/wayland.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/src/process/resources/skills-library/bodies/skills/productivity/systems-thinking-practitioner .opencode/skills/systems-thinking-practitioner && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "systems-thinking-practitioner" agent skill from https://github.com/FerroxLabs/wayland/tree/main/src/process/resources/skills-library/bodies/skills/productivity/systems-thinking-practitioner into .opencode/skills/systems-thinking-practitioner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "systems-thinking-practitioner", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
systems-thinking-practitionerApplied 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. 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.
6 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 4c030c7. It shows what the files ask for, not the result of running them.
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.
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.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
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.
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.
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.
The full file from FerroxLabs/wayland at commit 4c030c7, republished under its Apache-2.0 licence (© FerroxLabs). 414 words, ~3,146 tokens.
.claude/skills/systems-thinking-practitioner/SKILL.md (or your agent's skills folder).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.
Use this skill when:
Do NOT use when:
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: 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.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?"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 arenasSTEP-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)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)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 stepsPROBLEM: 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 workESSENTIAL 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## 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]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:
© 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
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
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Systems Thinking Practitioner this skillFerroxLabs/wayland | 608 | — | ~3.1k | Automated safety check: Pass | Apache-2.0 | |
| JSON Canvasheyitsnoah/claudesidian | 2.6k | 18 repos | ~3.5k | Automated safety check: Pass | MIT | |
| Archify Diagramstt-a1i/archify | 79k | — | ~2.9k | Automated safety check: Pass | MIT | |
| Diagram Designcathrynlavery/diagram-design | 44k | 1 repos | ~7.5k | Automated safety check: Pass | MIT | |
| Fireworks Tech Graphtisfeng/Easydict | 15k | 1 repos | ~1.4k | Automated safety check: Pass | MIT | |
| Excalidraw Diagramcoleam00/excalidraw-diagram-skill | 4.9k | 2 repos | ~6.1k | Automated safety check: Pass | None |
heyitsnoah/claudesidian
Create and edit JSON Canvas files (.canvas) with nodes, edges, groups, and connections.
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.
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.
tisfeng/Easydict
Create precise SVG technical diagrams, export PNG or offline HTML, and animate supported semantic SVGs to GIF.
coleam00/excalidraw-diagram-skill
Create Excalidraw diagram JSON files that make visual arguments.
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.
FerroxLabs/wayland
Install, start, connect, and troubleshoot visualization companion projects for Aion/OpenClaw, with Star-Office-UI as the default recommendation.
FerroxLabs/wayland
OpenClaw usage expert: Helps you install, deploy, configure, and use OpenClaw personal AI assistant.
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.
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.
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…
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…
Categories
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.
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.
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.
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.
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.
SKILL.md names no scripts, command-line tools or credentials: Systems Thinking Practitioner is instructions for the agent only.
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.
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.
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.
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.
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.
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.