conducting-chaos-engineering
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill conducting-chaos-engineeringThis skill enables Claude to design and execute chaos engineering experiments to test system resilience. It is used when the user requests help with failure injection, latency simulation, resource exhaustion testing, or resilience validation. The skill is triggered by discussions of chaos experiments (GameDays), failure injection strategies, resilience testing, and validation of recovery mechanisms like circuit breakers and retry logic. It leverages tools like Chaos Mesh, Gremlin, Toxiproxy, and AWS FIS to simulate real-world failures and assess system behavior.
Validation
81%| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
body_output_format | No obvious output/return/format terms detected; consider specifying expected outputs | Warning |
Total | 13 / 16 Passed | |
Implementation
20%This skill content reads more like a marketing description than actionable guidance. It explains what chaos engineering is and what Claude 'will do' rather than providing concrete configurations, commands, or executable examples. The lack of actual tool configurations (Chaos Mesh YAML, Toxiproxy configs, AWS FIS templates) and missing safety/rollback procedures make this skill ineffective for real chaos engineering work.
Suggestions
Replace abstract descriptions with executable examples: include actual Chaos Mesh manifests, Toxiproxy configuration snippets, or AWS FIS experiment JSON templates
Add explicit safety checkpoints and rollback procedures: chaos experiments are destructive operations that require abort conditions, blast radius limits, and recovery validation steps
Remove explanatory content about what chaos engineering is and what the skill 'empowers' - assume Claude knows these concepts and focus on project-specific configurations and constraints
Add references to separate files for tool-specific guides (e.g., CHAOS_MESH.md, TOXIPROXY.md) with detailed configurations and examples
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is verbose and explains concepts Claude already knows (what chaos engineering is, how tools work). Phrases like 'empowers Claude to act as a chaos engineering specialist' and explanations of basic concepts waste tokens without adding actionable value. | 1 / 3 |
Actionability | No concrete code, commands, or executable examples are provided. The examples describe what 'the skill will' do abstractly rather than showing actual Chaos Mesh manifests, Toxiproxy configurations, or AWS FIS experiment templates that could be executed. | 1 / 3 |
Workflow Clarity | The 'How It Works' section provides a 4-step sequence, but lacks validation checkpoints, rollback procedures, or feedback loops for error recovery. For destructive chaos experiments, missing safety gates and abort conditions is a significant gap. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but everything is inline with no references to detailed tool-specific guides, example configurations, or safety checklists that would benefit from separate files. | 2 / 3 |
Total | 6 / 12 Passed |
Activation
100%This is a well-crafted skill description that excels across all dimensions. It provides specific concrete actions, comprehensive trigger terms that users in this domain would naturally use, explicit guidance on both what the skill does and when to use it, and occupies a clear niche that won't conflict with other skills. The description uses proper third-person voice throughout.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'design and execute chaos engineering experiments', 'failure injection', 'latency simulation', 'resource exhaustion testing', 'resilience validation', and mentions specific tools like Chaos Mesh, Gremlin, Toxiproxy, and AWS FIS. | 3 / 3 |
Completeness | Clearly answers both what ('design and execute chaos engineering experiments to test system resilience') and when ('when the user requests help with failure injection, latency simulation...', 'triggered by discussions of chaos experiments'). Explicit trigger guidance is provided. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'chaos engineering', 'failure injection', 'latency simulation', 'resource exhaustion', 'resilience testing', 'GameDays', 'circuit breakers', 'retry logic', plus specific tool names that users familiar with the domain would mention. | 3 / 3 |
Distinctiveness Conflict Risk | Very clear niche with distinct triggers specific to chaos engineering domain. Terms like 'chaos experiments', 'GameDays', 'Chaos Mesh', 'Gremlin', 'Toxiproxy', and 'AWS FIS' are highly specific and unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.