Individual skill
s4h-ecology-carrying-capacity
Applies carrying capacity thinking to any system with limits — maps the ceiling, overshoot risk, and what happens when it is crossed. Use when asked about 'capacity limits', 'how much can this system handle', 'are we overloaded', 'growth ceiling', 'when do we hit the wall', or 'sustainable scale'.
skills/s4h-ecology-carrying-capacity/SKILL.md
Source commit a30df8b67698ccb03ef5e35d68c2eddc5321ad3f
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- Last checked
- Nov 5, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 240
- Repository last updated
- Jul 15, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- claude-code Repository topic
- claude-code-plugin Repository topic
- cognitive-frameworks Repository topic
- creativity Repository topic
- decision-making Repository topic
- ethics Repository topic
- mental-models Repository topic
- problem-solving Repository topic
- reasoning Repository topic
- systems-thinking Repository topic
- marketing Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 7,771 bytes
Read excerpt
# Ecology: Carrying Capacity
Every system operates within limits. Not all limits are visible — some only become apparent at the moment they are crossed, and by then the damage is already accumulating. The concept of carrying capacity (K) originated in population ecology, formalised through the logistic growth model: populations grow rapidly when resources are abundant, slow as they approach the ceiling, and crash or stabilise when they hit or exceed it. Arthur Tansley, who coined the term "ecosystem" in 1935, understood that any system is defined by the relationship between its components and their resource base. Howard Odum extended this to show that energy and material constraints are the ultimate governors of system scale.
The insight transfers directly beyond biology. Teams have a carrying capacity defined by coordination costs, management bandwidth, and information throughput. Platforms have carrying capacities bounded by network congestion, moderation costs, and trust erosion. Markets have carrying capacities constrained by willingness-to-pay, substitution, and regulatory tolerance. In all cases: the limit exists whether or not it has been named, and approaching it without awareness is how organisations walk into overshoot.
---
## Your Process
**Step 1: Define the System and the Resource Axis**
Name the system being analysed and identify the primary resource or condition that limits growth. The carrying capacity is always a constraint on something specific — not "capacity" in the abstract but a specific input, condition, or ceiling.
**Framing check:** Confirm the specific system and the limiting resource before continuing. State what you've identified in one sentence, then use `AskUserQuestion`: