Individual skill
s4h-systems-emergence-detection
Identifies system-level properties that exist nowhere in any individual component. Use when asked about 'emergent behavior', 'components are fine but the system isn't', 'why does the whole behave like this', or 'what creates this property'.
skills/s4h-systems-emergence-detection/SKILL.md
Source commit a30df8b67698ccb03ef5e35d68c2eddc5321ad3f
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- 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.
- 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
- engineering 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 · 5,212 bytes
Read excerpt
# Systems Emergence Detection
Emergent properties are the most important features of complex systems and the least designed for. They arise from interactions between components, not from the components themselves — which is why fixing individual parts often fails to fix system-level problems. Identifying emergence requires asking not what each component does, but what arises when they interact.
---
## Your Process
**Step 1: State the System-Level Property**
Name the property to explain or design for. Be precise: "the platform feels trustworthy", "the team produces poor decisions", "the market self-corrects". Vague properties produce vague analysis.
**Framing check:** Confirm the specific system and emergent property before continuing. State what you've identified — the actual system being analyzed and the property you are tracing — in one sentence, then use `AskUserQuestion`:
- **Question:** "I'm reading this as: [your one-sentence framing of the system and the emergent property in focus]. Is that right?"
- **Header:** "Framing"