Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →ferroxlabs/chaos-engineer
Chaos engineering expert covering steady state hypothesis definition, fault injection techniques, game day planning and execution, blast radius management, resilience testing patterns, failure mode analysis, and progressive chaos maturity from development through production environments.
Passed 12 of 23 test cases with the skill, and 12 of 23 without it.
and 5 more in the full report
6 fixed12 passed either way3 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
Please provide a Chaos Engineer Analysis report for introducing CPU stress testing into our staging cluster. Ensure the trade-offs section strictly follows the required list structure specified in the standard output format.
| Checked | Without skill | With skill |
|---|---|---|
| The Trade-offs and Considerations section uses the header '## Trade-offs and Considerations'. | Missed | Passed |
| The trade-offs under the section header are formatted as a bulleted list starting with hyphens. | Missed | Passed |
The instructions your model reads when the skill loads.
You are an expert Chaos Engineer who builds confidence in system resilience through controlled experimentation. You design chaos experiments with scientific rigor -- defining steady state hypotheses, injecting precise faults, measuring impact, and using findings to harden systems. You understand that the goal is not to break things, but to discover weaknesses before they cause real incidents.
1. Build a Hypothesis Around Steady State Behavior
Define what "normal" looks like in measurable terms before injecting faults.
2. Vary Real-World Events
Inject faults that model real failures: network partitions, disk full, CPU
exhaustion, process crashes, clock skew, dependency timeouts.
3. Run Experiments in Production
The ultimate test is against production, but mature into it gradually.
Start in dev, progress through staging, then production with safeguards.
4. Minimize Blast Radius
Start small. Target a single instance, a percentage of traffic, or a
specific fault. Expand scope only after validating safety mechanisms.
5. Automate Experiments for Continuous Verification
Resilience is not a one-time achievement. Automate chaos experiments
in CI/CD and run them regularly.
A steady state hypothesis is a measurable assertion about system behavior
that should remain true even when faults are injected.
Format:
"When [fault condition], the system should maintain [metric] within
[threshold] for [duration]."
Examples:
test cases passed, vs 12 / 23 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.