testing-chaos

Execute chaos engineering experiments to validate system resilience against intentional failures.

4|2|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/wojons/skills --skill testing-chaos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: testing-chaos
Source: https://github.com/wojons/skills/tree/main/skills/testing-chaos
Command: npx skills add https://github.com/wojons/skills --skill testing-chaos

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps ensure systems are robust and can withstand failures by proactively injecting faults and observing recovery mechanisms.

Core Features & Use Cases

  • Failure Injection: Simulate network issues, resource exhaustion, and service outages.
  • Resilience Validation: Test circuit breakers, retry logic, and failover mechanisms.
  • Use Case: Before a major launch, use this skill to simulate a database outage in a staging environment to verify that the system automatically fails over to a replica without significant user impact.

Quick Start

Use the testing-chaos skill to start network latency experiments.

Frequently Asked Questions about testing-chaos

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

FAQPage Schema
What is chaos engineering and how does fault injection validate system resilience?

Chaos engineering validates system resilience by intentionally injecting faults like network latency or service outages, then observing recovery mechanisms such as circuit breakers and failover logic to ensure systems withstand failures.

How do I test disaster recovery plans and automatic failover before a major launch?

Test disaster recovery plans by simulating database outages and service dependency failures in a staging environment to verify the system automatically fails over to replicas without significant user impact.

Can I simulate network latency and resource exhaustion to check system stability?

Yes, you can simulate network latency and resource exhaustion to check system stability by executing fault injection scenarios that test how applications handle degraded networks and depleted compute resources.

What is the best way to verify circuit breakers and retry logic under failure conditions?

The best way to verify circuit breakers and retry logic is by proactively injecting dependency failures and observing whether the system correctly trips breakers and retries requests without cascading failures.

Does chaos engineering require a staging environment to safely inject faults?

Chaos engineering is safest in a staging environment where you can inject faults and validate high availability requirements without risking production stability or causing real user impact.

When should I avoid running fault injection experiments on my system?

Avoid running fault injection experiments on production systems without robust monitoring and rollback plans, as resource exhaustion and service outages can cause unexpected downtime if recovery mechanisms are untested.