$npx -y skills add human-avatar/skills-for-humanity --skill s4h-ecology-keystone-speciesIdentifies the entities with disproportionate structural importance — whose removal would collapse the system. Use when asked 'who is critical here', 'what holds this together', 'single points of failure', 'what if we lose X', 'irreplaceable actors', or 'structural dependencies'.
| 1 | # Ecology: Keystone Species |
| 2 | |
| 3 | In 1966, ecologist Robert Paine removed a single predator — the ochre sea star (*Pisaster ochraceus*) — from an intertidal zone on the coast of Washington state. Within months, mussel populations exploded, crowding out barnacles, algae, and limpets. A system that had held twelve species collapsed to near-monoculture. Paine coined the term "keystone species" for organisms whose influence on the ecosystem is disproportionate to their biomass or abundance. Remove the keystone and the arch falls. |
| 4 | |
| 5 | The same structural logic applies in human systems. Every organisation, market, platform, or community has entities — people, roles, institutions, technologies, or relationships — whose contribution to system structure far exceeds their apparent size or weight. They are often not the largest or loudest actors. They are the connectors, the maintainers, the trust nodes, the bridges between otherwise disconnected clusters. When they leave, retire, burn out, or are restructured away, the system does not simply shrink — it reorganises, often badly. |
| 6 | |
| 7 | Keystone species analysis is not the same as identifying your most valuable people or assets. Value and structural indispensability are different properties. A top performer can be replaced by another top performer. A keystone cannot be replaced by a substitute — their structural position is what matters, and that position is a function of relationships, trust, and accumulated context that cannot be quickly transferred. |
| 8 | |
| 9 | --- |
| 10 | |
| 11 | ## Your Process |
| 12 | |
| 13 | **Step 1: Scope the System** |
| 14 | Define the system being analysed — its components, boundaries, and the type of structure you're mapping (an organisation, a supply chain, an ecosystem of partners, a technology stack, a community). The keystone analysis depends entirely on what structural relationships matter in this context. |
| 15 | |
| 16 | **Framing check:** Confirm the system and the structural question in focus before continuing. State what you've identified in one sentence, then use `AskUserQuestion`: |
| 17 | - **Question:** "I'm reading this as: [your one-sentence framing of the system and what structural relationships matter]. Is that right?" |
| 18 | - **Header:** "Framing" |
| 19 | - **Options:** |
| 20 | - **Yes — proceed** — framing is correct |
| 21 | - **Adjust** — one element is off; user will correct it before you continue |
| 22 | - **Reframe** — different situation than read; incorporate the correction before proceeding |
| 23 | |
| 24 | **Step 2: Map the Structural Roles** |
| 25 | Identify what kinds of structural work is being done in this system. Typical structural roles include: |
| 26 | - **Connectors** — link otherwise disconnected clusters; high bridging centrality |
| 27 | - **Maintainers** — keep shared infrastructure, knowledge, or norms functioning; often invisible until absent |
| 28 | - **Trust anchors** — held in high regard across parties that distrust each other; enable cooperation |
| 29 | - **Modulators** — regulate the intensity or direction of activity (predators that keep prey from overrunning resources) |
| 30 | - **Facilitators** — create conditions for others to function (nurse trees in ecology; onboarding roles in organisations) |
| 31 | |
| 32 | **Step 3: Identify Keystone Candidates** |
| 33 | For each major node in the system, run the disproportionality test: if this entity were removed, what would change? Map candidate keystones by applying three criteria: |
| 34 | 1. **Cascade potential** — would their removal trigger second- and third-order changes beyond their immediate connections? |
| 35 | 2. **Substitutability** — is there a ready substitute that holds the same structural position, or would the position go unfilled? |
| 36 | 3. **Invisibility** — do other actors underestimate this entity's structural contribution? Keystones are often underestimated because they make everything look easy. |
| 37 | |
| 38 | **Before narrowing:** Show the full candidate set to the user. Use `AskUserQuestion`: |
| 39 | - **Question:** "I've identified [N] keystone candidates. Before I assess which are most structurally critical, are there any you'd flag as especially important, or any I've missed?" |
| 40 | - **Header:** "Candidates" |
| 41 | - **Options:** |
| 42 | - **Proceed with your selection** — the set looks right |
| 43 | - **Flag one** — user will name a specific candidate to include or elevate |
| 44 | - **Add a missing one** — user will describe it |
| 45 | |
| 46 | **Step 4: Score Structural Disproportionality** |
| 47 | For the strongest candidates: estimate the ratio of structural impact to apparent size. A keystone is identified by high impact-to-size ratio, not by raw impact. Document the specific structural mechanism — what exactly does this entity do that others cannot or do not? |
| 48 | |
| 49 | **Step 5: Model Removal Scenarios** |
| 50 | For each keystone, trace what happens if they are removed — suddenly (crisis) versus gradu |