Run Chaos Experiment

Design and run chaos experiments using Litmus or Chaos Mesh. Test system resilience via controlled fault injection, validate hypothesis-driven tests, improve failure recovery. Use before major launches, after architecture changes, during GameDays or DR drills, to validate failure mode assumptions, or as part of an SRE maturity program.

45 stars 4 forksTesting & QA

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add pjt222/agent-almanac --skill run-chaos-experiment
Manual install
git clone --depth 1 https://github.com/pjt222/agent-almanac.git /tmp/agent-almanac
mkdir -p ~/.claude/skills
cp -r /tmp/agent-almanac/i18n/caveman-lite/skills/run-chaos-experiment ~/.claude/skills/run-chaos-experiment

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Run Chaos Experiment

Inject controlled failures to test and improve system resilience.

## When to Use

- Before major product launches (load testing)
- After architecture changes (validate resilience)
- GameDays or disaster recovery drills
- Validate assumptions about failure modes
- Part of an SRE maturity program

## Inputs

- **Required**: Kubernetes cluster (for Litmus or Chaos Mesh)
- **Required**: Steady-state definition (what "normal" looks like)
- **Required**: Hypothesis to test (e.g., "API stays available if one pod crashes")
- **Optional**: Observability stack (Prometheus, Grafana) to measure impact
- **Optional**: Rollback plan

## Procedure

### Step 1: Define Steady State and Hypothesis

Document normal system behavior:

```markdown
## Steady State Definition

### Service: API Gateway
- **Availability**: 99.9% (< 0.1% error rate)
- **Latency**: p95 < 200ms
- **Throughput**: 1000 req/s
- **Dependencies**: Database (Postgres), Cache (Redis), Auth Service

### Metrics
- `rate(http_requests_total{job="api"}[5m])`
- `histogram_quantile(0.95, rate(http_request_duration_seconds_bucket[5m]))`
- `rate(http_requests_total{status=~"5.."}[5m])`

## Hypothesis
**"If one API pod is killed, the remaining pods will handle the load with <5s
disruption and no increase in error rate."**

### Validation Criteria
- Error rate remains <1%
- p95 latency stays <300ms (50ms grace)
- Service recovers within 5 seconds
- No cascading failures to downstream services
```
Read the full skill on GitHub

Details

Skill name
run-chaos-experiment
Path
i18n/caveman-lite/skills/run-chaos-experiment/SKILL.md
License
MIT
Repo updated
18 November 2026

FAQ

What does the Run Chaos Experiment skill do?

Design and run chaos experiments using Litmus or Chaos Mesh. Test system resilience via controlled fault injection, validate hypothesis-driven tests, improve failure recovery. Use before major launches, after architecture changes, during GameDays or DR drills, to validate failure mode assumptions, or as part of an SRE maturity program.

How do I install the Run Chaos Experiment skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add pjt222/agent-almanac --skill run-chaos-experiment. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Run Chaos Experiment popular?

It lives in pjt222/agent-almanac, which has 45 GitHub stars and 4 forks, and is included in 1 curated skill list.

Related skills

Adapt Architecture

45

pjt222/agent-almanac

Execute structural metamorphosis using strangler fig migration, chrysalis phases, and interface preservation. Covers transformation planning, parallel running, progressive cutover, rollback design, and post-metamorphosis stabilization for system architecture evolution. Use when assess-form has classified the system as READY for transformation, when migrating from monolith to microservices, when replacing a core subsystem while dependents continue operating, or when any architectural change must be gradual rather than big-bang.

Software DevelopmentIn 1 list

Adaptic

45

pjt222/agent-almanac

Master skill composing the 5-step synoptic cycle for panoramic synthesis across multiple domains. Orchestrates meditate, expand-awareness, observe, awareness, integrate-gestalt, and express-insight into a coherent process that produces unified understanding rather than sequential compromise. Use when a problem genuinely spans 3+ domains and the interactions between domains matter more than depth in any one, when sequential analysis feels like compromise rather than integration, or before major architectural decisions affecting multiple stakeholders.

OtherIn 1 list

Add Puzzle Type

45

pjt222/agent-almanac

Scaffold a new puzzle type across all 10+ pipeline integration points in jigsawR. Creates the core puzzle module, wires it into the unified pipeline (generation, positioning, rendering, adjacency), adds ggpuzzle geom/stat layers, updates DESCRIPTION and config.yml, extends the Shiny app, and creates a comprehensive test suite. Use when adding a completely new puzzle type to the package or following the 10-point integration checklist to ensure nothing is missed end-to-end.

Testing & QAIn 1 list

Run Puzzle Tests

45

pjt222/agent-almanac

Run jigsawR test suite via WSL R. Supports full suite, filtered by pattern, or single file. Interprets pass/fail/skip counts and identifies failing tests. Never use `--vanilla` (renv needs `.Rprofile` to activate). Use after R source changes, after adding a puzzle type or feature, before commits, or when debugging a specific failure.

Testing & QAIn 1 list

Prepare Soil

45

pjt222/agent-almanac

Assess and improve garden soil through testing, amendment, composting, and biodynamic preparations. Covers jar test, spade test, earthworm count, amendment by soil type (clay, sandy, depleted, compacted), composting methods (hot, cold, vermicomposting), no-till practices, cover cropping, and biodynamic preparations 500-508. Use when starting a new garden bed, when plants underperform despite adequate water and light, when transitioning to organic or biodynamic practice, when soil has become compacted or depleted, or when building a composting system.

Testing & QAIn 1 list

Sharpen Knife

45

pjt222/agent-almanac

Sharpen and maintain knives using whetstones, field stones, and improvised abrasives. Covers blade anatomy, bevel assessment, whetstone technique (coarse to fine progression), stropping, sharpness testing, field sharpening methods, and ongoing edge maintenance. Use when a knife fails the fingernail test, when cutting tasks require excessive pressure, before a trip where a sharp blade is essential, after heavy use, or when a blade has visible nicks or a rolled edge. Applicable to bushcraft blades, folding knives, and garden cutting tools.

Testing & QAIn 1 list

Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.