Apply Complex Adaptive Systems theory to analyze phenomena exhibiting emergence, self-organization, co-evolution, and edge-of-chaos dynamics. Use this skill when the user needs to understand why a system behaves unpredictably despite known components, model agent-based interactions that produce emergent outcomes, analyze fitness landscapes, or when they ask 'why does this system behave in ways no one designed', 'how do local interactions create global patterns', or 'why do small changes sometimes cause massive system shifts'.
npx skills add https://github.com/asgard-ai-platform/skills --skill grad-cas
Complex Adaptive Systems are composed of diverse, autonomous agents that interact locally according to simple rules, producing emergent global behavior that cannot be predicted from individual components. CAS exhibit self-organization, co-evolution with their environment, and operate at the edge of chaos — the zone between rigid order and random disorder where adaptation and innovation are maximized.
IRON LAW: In a CAS, system behavior EMERGES from local interactions
and CANNOT be predicted by analyzing individual components — the whole
is fundamentally different from the sum of parts.
Key assumptions:
Define system boundaries. Identify the diverse agents, their decision rules, and their local interaction patterns.
Describe how agents interact: network structure, feedback loops (positive and negative), information flows, and resource dependencies.
Document system-level behaviors that no individual agent designed or intended. Look for self-organization, pattern formation, phase transitions, and attractors.
Analyze how agents modify their rules in response to outcomes, how the fitness landscape shifts through co-evolution, and whether the system operates near the edge of chaos.
## CAS Analysis: [Context]
### System Identification
- System boundary: [what is inside/outside the system]
- Agent types: [categories of autonomous actors]
- Agent rules: [simple behavioral rules agents follow]
### Interaction Topology
| Agent Type | Interacts With | Mechanism | Feedback Type |
|------------|---------------|-----------|---------------|
| [type] | [partners] | [how] | [positive/negative] |
### Emergent Properties
- Observed emergence: [system behaviors not designed by any agent]
- Self-organization: [spontaneous order that has formed]
- Phase transitions: [sudden shifts observed or possible]
### Adaptive Dynamics
- Co-evolution: [how agents and environment change together]
- Fitness landscape: [stable peaks / shifting / rugged]
- Edge of chaos assessment: [too rigid / adaptive zone / too chaotic]
### Implications
1. [Why top-down intervention may fail or succeed]
2. [Leverage points for influencing system behavior]
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Replace with description of the skill and when Claude should use it.
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
This skill should be used when the user wants to "create a skill", "add a skill to plugin", "write a new skill", "improve skill description", "organize skill content", or needs guidance on skill structure, progressive disclosure, or skill development best practices for Claude Code plugins.
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Take asgard-ai-platform/grad-cas from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.