Skip to content
TrustedSkillsbeta
Back to all skills

Backup Disaster Recovery

Checked
aj-geddes·vlatest·cloud·MIT

This skill creates automated backups & recovery plans to safeguard your data from disasters, ensuring business continuity and minimizing downtime.

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 backup-disaster-recovery -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

    Makes no network calls.

    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.

  • 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/backup-disaster-recovery/SKILL.md
Scanned
7 files, 536 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 backup-disaster-recovery skill enables AI agents to generate comprehensive strategies for data protection, including defining retention policies, selecting storage solutions, and creating step-by-step recovery playbooks. It assists in drafting incident response plans that outline communication protocols and technical procedures to minimize downtime during critical failures.

When to use it

  • Designing a new cloud infrastructure setup requiring robust data safety measures.
  • Creating an incident response plan for a team facing potential ransomware attacks.
  • Documenting standard operating procedures for restoring databases after accidental deletion.
  • Evaluating current backup protocols against industry best practices for compliance audits.

Key capabilities

  • Generating structured disaster recovery plans with clear phases and objectives.
  • Recommending specific retention schedules based on data criticality and regulatory needs.
  • Drafting technical runbooks detailing commands, tools, and verification steps for restoration.
  • Identifying potential single points of failure in existing backup architectures.

Example prompts

"Create a disaster recovery plan for a small e-commerce site using AWS S3 and RDS." "Draft a step-by-step playbook to restore our PostgreSQL database from the last successful snapshot." "What are the best practices for defining retention policies for financial transaction logs?"

Tips & gotchas

Ensure you provide context about your specific infrastructure (e.g., cloud provider, database type) so the generated plan is actionable. Remember that AI-generated recovery plans must be tested regularly in a staging environment to verify their effectiveness before a real incident occurs.