chaos-engineer

Automate resilience testing by injecting controlled failures into distributed systems.

8|11|Updated Feb 15, 2026
One-click install
npx skills add https://github.com/belokonm/claude-supercode-skills --skill chaos-engineer-belokonm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: chaos-engineer
Source: https://github.com/belokonm/claude-supercode-skills/tree/main/chaos-engineer-skill
Command: npx skills add https://github.com/belokonm/claude-supercode-skills --skill chaos-engineer-belokonm

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Chaos Engineer enables teams to systematically test and improve system resilience by injecting controlled failures and validating anti-fragile design.

Core Features & Use Cases

  • Experiment design: Define hypotheses, blast radius, and metrics.
  • Automated injection & rollback: Execute failovers and revert safely.
  • Metrics & reporting: Collect baseline/during/after data and generate reports.
  • Use Case: Validate that a microservices checkout path remains available during a database failover in production.

Quick Start

Run a basic chaos experiment in a non-production namespace to validate the setup.

Frequently Asked Questions about chaos-engineer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate resilience testing for distributed systems?

Automate resilience testing by designing chaos experiments with defined hypotheses, injecting controlled failures like database failovers, and validating system availability through automated execution and rollback.

What is chaos engineering and when do I need it for Kubernetes?

Chaos engineering is the systematic injection of controlled failures to validate system reliability. You need it for Kubernetes to test fault tolerance, ensure microservices availability during incidents, and validate disaster recovery preparedness.

How do I run a chaos experiment in a non-production environment?

Run a basic chaos experiment in a non-production namespace by defining a blast radius, executing fault injection, collecting baseline and during-incident metrics, and performing a safe rollback to validate your setup.

Can I validate microservices availability during a database failover in production?

Yes, you can validate that a microservices checkout path remains available during a database failover in production by defining metrics, executing the failover injection, and comparing baseline, during, and after data.

What metrics do I collect during a chaos engineering fault injection?

During fault injection, collect baseline, during-incident, and after-incident metrics to compare system behavior, validate resilience hypotheses, and generate comprehensive reports on system availability and recovery.

How do I design a chaos experiment with a safe blast radius?

Design a chaos experiment by defining clear hypotheses, setting a controlled blast radius to limit impact, selecting target services, and establishing automated rollback procedures to safely revert injected failures.