skills.rest
mytechsonamy
mytechsonamyCOMMUNITY
Explore all skills by this author →
GitHub

chaos-injector

Run controlled chaos injections against non-production environments with preflight health checks.

1|Updated Apr 12, 2026
Search Tags:#testing#resilience#observability#chaos#chaos-engineering#fault-injection
One-click install
npx skills add https://github.com/mytechsonamy/VibeFlow --skill chaos-injector
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: chaos-injector
Source: https://github.com/mytechsonamy/VibeFlow/tree/main/skills/chaos-injector
Command: npx skills add https://github.com/mytechsonamy/VibeFlow --skill chaos-injector

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Chaos injection helps teams evaluate resilience by intentionally breaking parts of a running system in a controlled, recoverable way.

Core Features & Use Cases

  • Controlled fault injection across networks, dependencies, clocks, and resources to observe degradation, recovery, and resilience scoring.
  • Stepwise execution with preflight health checks, per-injection observation, and mandatory recovery, ensuring safe, auditable experiments.
  • Use Case: In a staging environment, run a gentle latency spike or memory-pressure test to identify bottlenecks before release.

Quick Start

Invoke chaos-injector against a non-production environment with a chosen profile.

Frequently Asked Questions about chaos-injector

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

FAQPage Schema
How do I run chaos engineering tests in a staging environment safely?▼

Chaos engineering tests in staging are run safely by enforcing preflight health checks, executing stepwise fault injections, and mandating recovery before recording a resilience score.

What is controlled fault injection and how does it measure system resilience?▼

Controlled fault injection intentionally disrupts networks, dependencies, clocks, or resources in a recoverable way to observe system degradation and recovery, ultimately producing a measured resilience score.

Can I use chaos injection to simulate memory pressure and latency spikes before release?▼

Yes, you can inject gentle latency spikes or memory-pressure tests in non-production environments to identify system bottlenecks and observe degradation before a production release.

Does chaos testing require mandatory recovery steps during execution?▼

Chaos testing requires mandatory recovery steps as part of its stepwise execution to ensure experiments remain safe, auditable, and completely recoverable after each injection.

When should I not run fault injection experiments against my target environment?▼

Fault injection experiments should not be run against production environments; they are designed exclusively for non-production contexts like development and staging to avoid impacting customers.

What is the best way to audit chaos engineering experiments?▼

The best way to audit chaos engineering experiments is through stepwise execution that loads preflight health checks, monitors per-injection observations, and enforces mandatory recovery requirements.

Related Skills

Explore More Software Engineering Skills→
Growthub-aiGrowthub-ai
48

growthub-t3code-harness

Manage T3 Code harness health checks, prompts, and sessions within Growthub.

Official
Advanced
zscalerzscaler
44

zdx-analyze-application-health

Analyze organization-wide application health using ZDX scores and metrics.

Official
Advanced
doanchienthangdevdoanchienthangdev
4

testing/chaos-testing

Inject network, service, and database faults to test system resilience.

Community
Advanced
Design-System-ETDesign-System-ET

chaos-engineer

Design and execute chaos experiments to validate system resilience in distributed environments.

Official
Advanced