agentleFS
Sign inStart free
jackson2wjackson2w/claude-code-skills/forced-outage-drill/SKILL.md

forced-outage-drill

Skill1 starsChanged 9 days agoNo licenceView on GitHub

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".

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 1 is distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free