Menu
Controlled failure injection: hypothesis design, blast radius control, safety mechanisms, game day planning, and resilience verification.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Session bootstrap + workflows for Pathfinder semantic navigation tools. Covers: discovery protocol, tool chaining patterns (explore, impact, audit, debug), search optimization, LSP degraded mode, and error recovery.
Playwright browser automation via MCP. Covers E2E testing, UI review, web scraping, screenshot capture, and general browser interaction. MCP-first — CLI is fallback only.
Safe command execution: input sanitization, timeout handling, output capture, error propagation. For spawning processes, shell commands, system calls.
Git conventions: conventional commits, branch naming, PR hygiene, release tagging.
Structured incident workflow: severity classification, triage, diagnosis, mitigation, postmortem, and prevention. Template-driven with blameless review.
Constructs, validates, and traverses a Directed Acyclic Graph (DAG) from scope cards for safe level-based parallel dispatch. Determines execution order via topological sort. Detects cycles and invalid dependencies.
| name | chaos-testing |
| description | Controlled failure injection: hypothesis design, blast radius control, safety mechanisms, game day planning, and resilience verification. |
Controlled failure injection to build confidence in system resilience.
Identify measurable indicators of normal system behavior:
"When [failure condition], the system will [expected behavior] because [mechanism]."
Example: "When database primary fails, the system will failover to replica within 30s because of automatic failover configuration."
| Element | Description |
|---|---|
| Target | Which component to perturb |
| Failure mode | What kind of failure (latency, crash, partition) |
| Blast radius | Scope of impact (single instance, AZ, region) |
| Duration | How long the failure persists |
| Abort criteria | When to immediately stop the experiment |
| Rollback plan | How to restore normal operation |
| Type | Examples |
|---|---|
| Process | Kill process, OOM, CPU spike |
| Network | Latency injection, packet loss, partition |
| Infrastructure | Instance termination, AZ failure, disk full |
| Application | Exception injection, slow dependency, config error |
| Data | Corrupt cache, stale data, schema mismatch |
