scriptoriumadmin/claude-skills
1
0
Fork 0
mirror of https://github.com/alirezarezvani/claude-skills.git synced 2026-10-09 03:17:54 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions
claude-skills/engineering/chaos-engineering
History
Exact
Claude 0f88555485
chore(versioning,docs): normalize stale versions to 2.9.0 + refresh counts 
Version normalization (scope: only plugins/skills older than 2.7.0):
- Bumped 52 plugin.json + 21 SKILL.md `version` fields from pre-2.7.0
  values (1.0.0 / 2.0.x / 2.2.x / 2.3.x / 2.4.x / 2.5.x) to 2.9.0.
  Left 2.7.0+ packages untouched. Tool mirrors (.codex/.gemini/.vibe/
  .hermes) excluded. All manifests still pass check_plugin_json --all.

Doc count refresh (recomputed raw figures: 338 skills, 16 domains,
62 plugins, 533 Python tools, 676 references):
- marketplace.json: both descriptions + metadata.version -> 2.9.0.
- Root README: headline, badges (Skills 338, Agents 51+, Commands 87+),
  intro counts, convert section (338 skills / 9 tools), and the full
  domain table rebuilt to 16 domains summing to 338 (adds research-ops,
  business-operations, commercial, compliance-os; corrects product 17,
  marketing 46, c-level 66, ra-qm 18, finance 4, engineering 51/78).
- Fixed stale per-skill README `Version:` lines left inconsistent by the
  bump (andreessen, c-level-agents, product-team, senior-qa).
- Fixed stale domain README footers (product-team 17/17, c-level 66/66,
  project-management 9/9).
- CLAUDE.md scope line, structure tree, highlight, and footer synced to
  the raw figures.

https://claude.ai/code/session_01PUNmQVE4WYvcrzpq2anC3D
2026-05-27 05:22:59 +00:00
..
.claude-plugin chore(versioning,docs): normalize stale versions to 2.9.0 + refresh counts 2026-05-27 05:22:59 +00:00
skills/chaos-engineering chore(versioning,docs): normalize stale versions to 2.9.0 + refresh counts 2026-05-27 05:22:59 +00:00
README.md feat(skills): ship chaos-engineering (Phase 3 — resilience testing discipline) 2026-05-09 21:24:16 +00:00

README.md

Chaos Engineering

End-to-end discipline for chaos experiments — design, run, learn — without becoming an outage.

What's inside

  • 3 stdlib Python tools — experiment designer, blast-radius calculator, postmortem generator
  • 4 reference docs — principles, experiment design, attack taxonomy, tooling landscape
  • 2 templates — experiment plan, postmortem
  • /chaos-experiment slash command — interactive design wizard

Install

# Via Claude Code marketplace
/plugin install chaos-engineering

# Or clone the repo
git clone https://github.com/alirezarezvani/claude-skills.git
cd claude-skills/engineering/chaos-engineering

Quick start

SKILL=engineering/chaos-engineering/skills/chaos-engineering

# 1. Design an experiment
python "$SKILL/scripts/experiment_designer.py" \
  --target checkout-svc \
  --hypothesis "p99 < 500ms when payment slows" \
  --attack latency --magnitude "+200ms" \
  --abort-if "p99 > 1000ms OR error_rate > +1pp"

# 2. Calculate blast radius
python "$SKILL/scripts/blast_radius_calculator.py" \
  --traffic-share 0.05 --user-pop 1000000 \
  --duration-min 15

# 3. Generate postmortem after running
python "$SKILL/scripts/experiment_postmortem.py" \
  --plan plan.json --result-log results.txt

Key principles

  1. Build a hypothesis around steady-state behavior — measurable, falsifiable
  2. Vary real-world events — realistic failures only, not astronomy-grade
  3. Run experiments in production — staging never has prod failure modes
  4. Automate experiments to run continuously — single experiment = press release; continuous = engineering
  5. Define abort criteria up front — chaos without abort = outage

The 7 attack types

Attack Tests Magnitude examples
Latency Timeouts, retries, circuit breakers +200ms, +2s
Error Error handling, fallback paths 1%, 50%, 100%
Resource Saturation, autoscaling, OOM 80% CPU, 90% memory, fill /var
Network partition Consensus, leader election, failover drop 100% to peer X
Dependency failure Graceful degradation timeout 100% to dep X
Time skew Clocks, TTLs, retry backoff +5min, +1day
Infrastructure Auto-recovery, replica maintenance kill 1 of N

Composition with other skills

Skill Composition
feature-flags-architect Kill switches there are abort triggers here
kubernetes-operator Operators are common chaos targets
incident-response Chaos that escalates becomes an incident

Skill structure

chaos-engineering/
├── README.md
├── .claude-plugin/plugin.json
└── skills/chaos-engineering/
    ├── SKILL.md
    ├── scripts/
    │   ├── experiment_designer.py
    │   ├── blast_radius_calculator.py
    │   └── experiment_postmortem.py
    ├── references/
    │   ├── chaos_principles.md
    │   ├── experiment_design.md
    │   ├── attack_taxonomy.md
    │   └── tooling_landscape.md
    └── assets/
        ├── experiment_template.md
        └── postmortem_template.md

Verifiable success

A team using this skill should achieve:

  • 100% of chaos experiments have written hypothesis, abort criteria, blast-radius calc
  • Blast radius for any single experiment ≤10% of monthly error budget
  • Mean time between chaos experiments <14 days (continuous, not one-off)
  • Each experiment produces ≥1 follow-up action that gets shipped
  • No chaos experiment escalates to a customer-impacting incident in trailing 90 days

License

MIT — see repo root LICENSE.