running-chaos-tests

Quick Review

The skill provides a structured approach to chaos engineering testing with clear steps and error handling. However, it suffers from significant issues: (1) The description and content focus on generic 'testing' rather than chaos engineering specifics (failure injection, resilience testing, blast radius control), making it unclear how to trigger chaos experiments; (2) Novelty is low since chaos testing typically involves running specialized tools (like Chaos Toolkit, Gremlin, or LitmusChaos) that a CLI agent could invoke directly; (3) The allowed-tools constraint 'Bash(test:chaos-*)' suggests chaos-specific scripts exist but no concrete chaos patterns (network latency, pod killing, resource exhaustion) are documented; (4) Minor structural issues include a redundant 'Overview' section. The skill reads more like a generic test runner than a chaos engineering specialist that would meaningfully reduce token costs for complex resilience testing scenarios.