Individual skill

s4h-ecology-keystone-species

Identifies 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'.

skills/s4h-ecology-keystone-species/SKILL.md

Read pinned source

Source commit a30df8b67698ccb03ef5e35d68c2eddc5321ad3f

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Instructions only
Last checked
Nov 11, 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)
241
Repository last updated
Jul 15, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Ecology: Keystone Species

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.

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.

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.

---

## Your Process

**Step 1: Scope the System**
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.
Back to top