How do I install the Chaos Runner skill?

Run npx skillmds@latest add andersonlimahw/chaos-runner in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Chaos Runner safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Chaos Runner?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Chaos Runner free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Chaos Runner?

Andersonlimahw (@andersonlimahw) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Chaos Runner by andersonlimahw — Agent Skill

Name: Chaos Runner
Rating: 4.2 (5 reviews)
Author: Andersonlimahw

Chaos Runner

Chaos experiment orchestration and scheduling. Runs predefined chaos scenarios (latency injection, pod kill, dependency outage), records results, and tracks resilience score over time. Use when scheduling a game day, setting up weekly chaos tests, or verifying that a new circuit breaker works under fault conditions.

File contents

Chaos Runner Plugin

Scheduled fault injection. Automated resilience scoring.

Commands

/chaos-runner run <experiment>   — execute a named experiment
/chaos-runner schedule weekly    — schedule weekly chaos (random pod kill)
/chaos-runner history            — show past experiment results
/chaos-runner score              — current resilience score (0-100)
/chaos-runner game-day           — orchestrate a full game day session

Experiment Library

Pre-built experiments (run by name):

Name	What It Does
`pod-kill`	Kills a random pod from target deployment
`db-latency-500ms`	Adds 500ms to all DB connections via toxiproxy
`api-timeout`	Makes payment API time out after 3s
`disk-pressure`	Fills disk to 90% on one node
`memory-hog`	Allocates 80% of available heap
`network-partition`	Blocks all traffic between service A and B

Game Day Orchestration

/chaos-runner game-day

Phase 1 — Baseline (10 min)
  → Measure: p95 latency, error rate, uptime
  → Confirm steady state

Phase 2 — Experiment (30 min)
  → Run: db-latency-500ms
  → Monitor: circuit breakers, fallbacks, error messages

Phase 3 — Recovery (10 min)
  → Remove fault
  → Confirm return to steady state

Phase 4 — Report
  → Resilience score: 78/100
  → Failed: circuit breaker opened too slowly (12s, target <5s)
  → Action item: reduce CB threshold from 10 failures to 5

Resilience Score

RESILIENCE SCORE — 2026-06-14
================================
Total: 78/100

Detection speed:   85/100  (alert in 2min, target <3min) ✅
Recovery speed:    70/100  (recovered in 4min, target <2min) ⚠️
Blast radius:      90/100  (only /checkout affected, not /browse) ✅
User experience:   65/100  (users saw 500 instead of fallback message) ❌
Circuit breaker:   80/100  (opened correctly, but closed too fast) ⚠️

Pairs with /chaos-test skill for experiment design.

---name: chaos-runnerdescription: Chaos experiment orchestration and scheduling. Runs predefined chaos scenarios (latency injection, pod kill, dependency outage), records results, and tracks resilience score over time. Use when scheduling a game day, setting up weekly chaos tests, or verifying that a new circuit breaker works under fault conditions.---# Chaos Runner PluginScheduled fault injection. Automated resilience scoring.## Commands```/chaos-runner run <experiment> — execute a named experiment/chaos-runner schedule weekly — schedule weekly chaos (random pod kill)/chaos-runner history — show past experiment results/chaos-runner score — current resilience score (0-100)/chaos-runner game-day — orchestrate a full game day session```## Experiment LibraryPre-built experiments (run by name):| Name | What It Does ||------|-------------|| `pod-kill` | Kills a random pod from target deployment || `db-latency-500ms` | Adds 500ms to all DB connections via toxiproxy || `api-timeout` | Makes payment API time out after 3s || `disk-pressure` | Fills disk to 90% on one node || `memory-hog` | Allocates 80% of available heap || `network-partition` | Blocks all traffic between service A and B |## Game Day Orchestration```/chaos-runner game-dayPhase 1 — Baseline (10 min) → Measure: p95 latency, error rate, uptime → Confirm steady statePhase 2 — Experiment (30 min) → Run: db-latency-500ms → Monitor: circuit breakers, fallbacks, error messagesPhase 3 — Recovery (10 min) → Remove fault → Confirm return to steady statePhase 4 — Report → Resilience score: 78/100 → Failed: circuit breaker opened too slowly (12s, target <5s) → Action item: reduce CB threshold from 10 failures to 5```## Resilience Score```RESILIENCE SCORE — 2026-06-14================================Total: 78/100Detection speed: 85/100 (alert in 2min, target <3min) ✅Recovery speed: 70/100 (recovered in 4min, target <2min) ⚠️Blast radius: 90/100 (only /checkout affected, not /browse) ✅User experience: 65/100 (users saw 500 instead of fallback message) ❌Circuit breaker: 80/100 (opened correctly, but closed too fast) ⚠️```Pairs with `/chaos-test` skill for experiment design.

Frequently asked questions