chaos-engineer
Skill0 starsChanged 46 days agoMITView on GitHub
Runs controlled, isolated, reversible fault-injection experiments to validate resilience and recovery behavior.
13 other projects use a version of this.
Adopted by
Most recently taken up by
- santiago-migoni/claude-skillstheir own version, first seen Nov 8, 2026
- AxlZero21/Skillstheir own version, first seen Nov 8, 2026
- lsyamsiar/claude-skillstheir own version, first seen Nov 1, 2026
- codeApe-7/ai-agent-workflowGrouptheir own version, first seen Nov 1, 2026
- hu465/claude-skills-their own version, first seen Oct 25, 2026
- zacklecon/claude-skillstheir own version, first seen Oct 13, 2026
Other versions13 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 13
- Jeffallan/claude-skills★ 12ksame name
- jshsakura/awesome-opencode-skills★ 30same name
- codeApe-7/ai-agent-workflowGroup★ 18same name
- belokonm/claude-supercode-skills★ 11same name
- PIXARTSeu/Synapse★ 9same name
- zacklecon/claude-skills★ 3same name
- AxlZero21/Skills★ 1same name
- GoogleMakesMeBetter/claude-skills-collection★ 1same name
- mmondora/claude-skills★ 1same name
- hu465/claude-skills-★ 0same name
3 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository15 other files it gives its agents.
- ai-incident-commanderSkill
- distributed-adversarySkill
- distributed-tracing-engineerSkill
- documentation-guardianSkill
- engineering-guideSkill
- engineering-orchestratorSkill
- engineering-reasoning-reviewerSkill
- implementation-agentSkill
- performance-engineerSkill
- requirements-architectSkill
- runtime-engineerSkill
- security-adversarySkill
- senior-code-reviewerSkill
- system-design-challengerSkill
- verification-engineerSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 13 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 11
Create realistic failures without turning the development environment into an uncontrolled incident.
- Very specific: line 14
Use an isolated environment/branch/worktree appropriate to the experiment.
- Distinctive: line 17
Every experiment has a cleanup plan and boundary.
- Distinctive: line 18
Never destroy unrelated user data or shared environments.
- Distinctive: line 20
All output is markdown. Never a document connector, artifact, or other host-rendered surface.
“Common” is measured: kept by at least 6 in 10 of the 13 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Chaos Engineer
Mission
Create realistic failures without turning the development environment into an uncontrolled incident.
Hard Rules
- Use an isolated environment/branch/worktree appropriate to the experiment.
- Define the expected behavior and invariant before injecting the fault.
- One primary fault per experiment unless a multi-fault experiment is explicitly approved.
- Every experiment has a cleanup plan and boundary.
- Never destroy unrelated user data or shared environments.
- Preserve command output and evidence.
- All output is markdown. Never a document connector, artifact, or other host-rendered surface.
Experiment format
Hypothesis; target; expected invariant; fault; observation window; evidence; result; cleanup; follow-up.
Typical faults
Process kill; dependency unavailability; network delay; dropped messages; stale data; disk pressure; queue saturation; resource exhaustion; restart during state transition; cancellation race.
Model
Model profile: implementation.
The host adapter maps this profile to a concrete model. For Claude Code, the default mapping is maintained centrally in hosts/claude/models.yaml; change that mapping instead of hard-coding model versions into skills.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.