Back to catalog
Human reviewedDevelopment

Skill dossier

chaos-engineer

Source declaration

Designs chaos experiments, creates failure injection frameworks, and facilitates game day exercises for distributed systems — producing runbooks, experiment manifests, rollback procedures, and post-mortem templates. Use when designing chaos experiments, implementing failure injection frameworks, or conducting game day exercises. Invoke for chaos experiments, resilience testing, blast radius control, game days, antifragile systems, fault injection, Chaos Monkey, Litmus Chaos.

The author's original description, preserved in English. It describes intent, not verified performance.

Designs chaos experiments, creates failure injection frameworks, and facilitates game day exercises for distributed systems — producing runbooks, experiment manifests, rollback procedures, and post-mortem templates. Use when designing chaos experiments, implementing failure injection frameworks, or conducting game day exercises. Invoke for chaos experiments, resilience testing, blast radius control, game days, antifragile systems, fault injection, Chaos Monkey, Litmus Chaos.

developmentreferences

Research summary

Human reviewed

Skill Atlas editorial review · editorial-preview-1.0.0

Designs chaos experiments and game days with an explicit hypothesis, steady state, blast radius and rollback, with Litmus, toxiproxy and Chaos Monkey examples.

Review scope

Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.

Observable capabilities

  • Maps architecture, dependencies and failure modes before designing an experiment.
  • Defines hypothesis, steady state, blast radius and safety controls.
  • Produces failure-injection manifests and scripts, such as a Litmus ChaosEngine for pod deletion.
  • Documents findings with a learning summary and at least one tracked improvement.

Limitations & scope

  • Examples target Kubernetes, toxiproxy and Chaos Monkey; other stacks are not covered in the file.
  • Running experiments requires real infrastructure access, which this review did not exercise.
  • The 30-second rollback target is a stated rule, not something verified here.

Relevant for

  • SRE and platform engineers
  • Teams planning game days
  • Engineers testing resilience of distributed systems

What ships with the skill

The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.

files
6
Markdown files
6
scripts
0
references
5
Size
60.1 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/chaos-engineer/references/chaos-tools.mdReference13.9 KB
skills/chaos-engineer/references/experiment-design.mdReference6.9 KB
skills/chaos-engineer/references/game-days.mdReference12.1 KB
skills/chaos-engineer/references/infrastructure-chaos.mdReference9.8 KB
skills/chaos-engineer/references/kubernetes-chaos.mdReference10.5 KB
skills/chaos-engineer/SKILL.mdInstruction6.9 KB

SKILL.md frontmatter

{
  "name": "chaos-engineer",
  "description": "Designs chaos experiments, creates failure injection frameworks, and facilitates game day exercises for distributed systems — producing runbooks, experiment manifests, rollback procedures, and post-mortem templates. Use when designing chaos experiments, implementing failure injection frameworks, or conducting game day exercises. Invoke for chaos experiments, resilience testing, blast radius control, game days, antifragile systems, fault injection, Chaos Monkey, Litmus Chaos.",
  "license": "MIT",
  "metadata": {
    "author": "https://github.com/Jeffallan",
    "company": "https://synergetic.solutions",
    "version": "1.1.0",
    "domain": "devops",
    "triggers": "chaos engineering, resilience testing, failure injection, game day, blast radius, chaos experiment, fault injection, Chaos Monkey, Litmus Chaos, antifragile",
    "role": "specialist",
    "scope": "implementation",
    "output-format": "code",
    "related-skills": "sre-engineer, devops-engineer, kubernetes-specialist"
  }
}

A reading of the operating sequence

This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.

  1. 01
    Input

    Analyze the system

    Map architecture, dependencies, critical paths and failure modes.

  2. 02
    Action

    Design the experiment

    Define hypothesis, steady state, blast radius and safety controls.

  3. 03
    Decision

    Enforce the safety checklist

    Require a scripted automated rollback of 30 seconds or less before the experiment begins.

  4. 04
    Output

    Deliver experiment package

    Provide the design document, injection code, monitoring setup, rollback procedures and a learning summary.

Potential risk surfaces

Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.

Attention recommended

58 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.

Network accessObserved
File writesObserved
Credential useObserved
High

Credential or secret material is referenced

3 occurrences

This line resembles a credential literal or reads a sensitive environment value. Do not expose its contents; verify whether it is a placeholder, required secret, or accidentally committed material. This rule matched 3 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Medium

Network access is mentioned

21 occurrences

A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 21 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Note

File modification is described or implemented

31 occurrences

This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 31 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

High

Elevated privileges are referenced

3 occurrences

Privilege-elevation syntax is present. Confirm whether elevation is necessary and inspect every operation performed under it; static analysis cannot prove that elevation succeeded. This rule matched 3 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Editorial security note

Never run its failure-injection commands against production without safety nets and explicit approval, and review each manifest first.

Where context can be spent

Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.

Exact token counts unavailable

All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.

No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.

Controlled evaluation

No controlled evaluation

This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.

Not tested

Use with the source in view

Install command
git clone https://github.com/Jeffallan/claude-skills.git cd claude-skills # Copy this skill directory into one of: # ~/.claude/skills/chaos-engineer # .claude/skills/chaos-engineer
  1. Open the pinned source at https://github.com/Jeffallan/claude-skills/blob/67c1961b180dc92cf08983344627109e983e8f51/skills/chaos-engineer/SKILL.md.
  2. Review the license, prerequisites and all bundled reference files.
  3. Install the skill into a personal or project-level Claude Code skills directory.
  4. Restart or refresh Claude Code so the skill can be discovered.
Verify installation

Confirm chaos-engineer/SKILL.md exists at the destination, then ask Claude Code to use the chaos-engineer skill on a small test task.

Prerequisites

  • Examples target Kubernetes, toxiproxy and Chaos Monkey; other stacks are not covered in the file.
  • Running experiments requires real infrastructure access, which this review did not exercise.
  • The 30-second rollback target is a stated rule, not something verified here.

Example prompts

Representative task

Use the chaos-engineer skill to design a pod-delete experiment for my-service in a staging cluster with a steady-state check, a 33% blast radius cap and a tested abort command.

Inspect before use

Read the chaos-engineer skill at https://github.com/Jeffallan/claude-skills/blob/67c1961b180dc92cf08983344627109e983e8f51/skills/chaos-engineer/SKILL.md and its referenced files. Explain its workflow, required tools, permissions and the main risks before I decide whether to install it.

A decision, with its limits attached

Strengths

  • Safety checklist requires steady state first, a capped blast radius and a scripted abort path.
  • Examples include explicit abort and rollback commands.

Considerations

  • Examples run kubectl against a production namespace, so they must be adapted carefully.
  • Requires monitoring and rollback tooling to exist before it adds value.
Research conclusion

A safety-first chaos engineering guide that is only appropriate where observability and rollback already exist.

Traceable by construction

The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.

Jeffallanclaude-skillsskills/chaos-engineer
Source type
Community
Commit
67c1961b180dc92cf08983344627109e983e8f51
Collected
20 Nov 2026
Last checked
20 Nov 2026
Upstream license
MIT
Repository stars
12,464
Content basis

Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.