Skip to content

jackson2w/claude-code-skills / forced-outage-drill

forced-outage-drill

Flagged

Simulate a dependency outage on a live host (upstream DNS, an API endpoint, a backup target, a peer) to prove a watcher, failover or alert actually works, without paging anyone and without the drill passing for the wrong reason. Covers proving the block bites (nft counters plus a control) before trusting any result, why container egress needs a forward-hook chain, cache and stale-answer layers that hide the outage, a systemd-run dead-man revert, testing a new watcher against a throwaway instance on a spare port with stubbed alerting, and the drill sequence: baseline, failure surfaces, failover, recovery, cleanup. Trigger phrases include "failover drill", "simulate an outage", "force a failover", "test the watcher", "blackhole the upstream", "nft drop for a test", "dead-man revert", "does the alert actually fire", "drill without paging", "stub telegram", "prove the failover works".

finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the workStars: 322kUpdated Claude CodeCodexVerifiedInstall
systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesStars: 322kUpdated Claude CodeCodexVerifiedInstall
test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation codeStars: 322kUpdated Claude CodeCodexVerifiedInstall
skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.Stars: 198kUpdated Claude CodeCodexVerifiedInstall