Skip to content
TrustedSkillsbeta
Back to all skills

Disaster Recovery Testing

Checked
aj-geddes·vlatest·testing·MIT

Simulates disaster scenarios to validate data recovery plans and system resilience automatically.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add aj-geddes/useful-ai-prompts --skill disaster-recovery-testing -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

aj-geddes

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Only contacts known or declared hosts: myapp-dr.internal.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

    Hosts contacted

    myapp-dr.internallocal

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned aj-geddes/useful-ai-prompts at 3f5182cfd7.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
3f5182cfd7
Manifest
skills/disaster-recovery-testing/SKILL.md
Scanned
6 files, 475 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

The disaster-recovery-testing skill enables AI agents to systematically validate recovery procedures and verify system resilience against catastrophic failures. It automates the execution of predefined test scenarios to ensure that backup strategies and failover mechanisms function correctly when primary systems go offline.

When to use it

  • Validating the integrity of automated backup restoration processes before a real incident occurs.
  • Simulating specific failure modes, such as database corruption or network partitioning, to test agent responses.
  • Verifying that critical business continuity plans can be executed within required Recovery Time Objectives (RTO).
  • Auditing disaster recovery configurations to ensure compliance with organizational security and operational standards.

Key capabilities

  • Automated execution of disaster recovery playbooks.
  • Verification of data restoration accuracy from backup sources.
  • Simulation of various failure scenarios to stress-test system resilience.
  • Generation of detailed reports on recovery success rates and bottlenecks.

Example prompts

  • "Run a full disaster recovery simulation for our primary database cluster and report any discrepancies found during the restore process."
  • "Test the failover mechanism by simulating a complete node outage and verify that services switch to the secondary region within 5 minutes."
  • "Execute the quarterly backup validation script and confirm that all critical data sets can be successfully restored to the staging environment."

Tips & gotchas

Ensure your disaster recovery infrastructure is isolated from production environments during testing to prevent accidental data loss or service disruption. Always review generated test reports thoroughly, as automated simulations may not catch every edge case inherent in complex human-operated recovery procedures.