QE Chaos Resilience

Orchestrate chaos engineering experiments with fault injection and resilience validation.

2|2|Updated Aug 23, 2025
One-click install
npx skills add https://github.com/summarybotng/summarybot-ng --skill qe-chaos-resilience
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: QE Chaos Resilience
Source: https://github.com/summarybotng/summarybot-ng/tree/main/.claude/skills/qe-chaos-resilience
Command: npx skills add https://github.com/summarybotng/summarybot-ng --skill qe-chaos-resilience

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill addresses the critical need to proactively identify and mitigate system weaknesses before they impact users by simulating real-world failures and stress conditions.

Core Features & Use Cases

  • Chaos Engineering: Design and execute controlled fault injection experiments (e.g., network latency, packet loss, resource exhaustion).
  • Load & Stress Testing: Simulate high traffic scenarios to identify performance bottlenecks and breaking points.
  • Resilience Validation: Verify system recovery mechanisms, graceful degradation, and disaster preparedness.
  • Use Case: A team can use this Skill to simulate a database outage during off-peak hours, observe how the application handles the failure, and confirm that it automatically recovers once the database is restored, all without impacting live users.

Quick Start

Run a chaos experiment to inject 500ms network latency into the api-service.

Frequently Asked Questions about QE Chaos Resilience

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

FAQPage Schema
What is chaos engineering and how does fault injection testing work?

Chaos engineering uses controlled fault injection to simulate real-world failures like network latency or resource exhaustion, proactively identifying system weaknesses and mitigating adverse conditions before they impact users.

How do I test system resilience and disaster recovery under high traffic load?

You can validate system resilience by simulating high traffic stress testing scenarios to identify performance bottlenecks, verify graceful degradation, and confirm automated recovery mechanisms function correctly under adverse conditions.

Can I validate circuit breaker behavior and SLA compliance during a database outage?

Yes, you can simulate a database outage to observe application failure handling, verify circuit breaker validation, and perform automated SLA compliance checks using defined safety guardrails without impacting live users.

What is the best way to run a chaos experiment without impacting live users?

The best approach is to orchestrate controlled fault injection experiments during off-peak hours, utilizing defined safety guardrails to ensure system stability and automated recovery validation without disrupting production traffic.

Does this chaos engineering approach support automated recovery testing and graceful degradation validation?

Yes, it supports automated recovery testing and graceful degradation validation by orchestrating stress conditions, confirming that the system automatically recovers once failures are resolved, and generating detailed reporting on resilience.

When should I not use chaos engineering and fault injection experiments?

You should avoid running fault injection experiments without defined safety guardrails in place, as uncontrolled resource exhaustion or network latency simulations risk destabilizing the system and impacting live users.