backup-disaster-recovery — Claude Code skill: backups and recovery
A skill that helps the agent plan database backups, disaster recovery and cross-region failover for your infrastructure.
npx skills add aj-geddes/useful-ai-prompts --skill backup-disaster-recovery -a claude-codeWhat backup-disaster-recovery does
This skill walks the agent through backup and disaster recovery work: scheduled backups, more than one storage location, integrity checks, written recovery steps. The quick start shows a Kubernetes cronjob that dumps a PostgreSQL database on a schedule.
The detail sits in the references/ directory: database backup configuration, a disaster recovery plan template, a backup and restore script, and cross-region failover. The agent pulls the file that matches your stack when you ask for a procedure.
The skill tells you to keep encryption keys away from the backups themselves and not to park copies next to production data. If all your copies live in one place and nobody has ever restored one, start with a restore test rather than a new schedule.
What it helps with
- set up a backup schedule for a database
- write a disaster recovery plan
- verify that a backup actually restores
- configure cross-region failover
- document point-in-time recovery steps
Example prompts for the agent
- write a backup plan for PostgreSQL on Kubernetes
- generate a backup and restore script for our database
- review our disaster recovery plan and find the gaps
How to install backup-disaster-recovery
1Skills CLI (Vercel)
npx skills add aj-geddes/useful-ai-prompts --skill backup-disaster-recovery -a claude-code2Manually: put the files in place
~/.claude/skills/backup-disaster-recovery/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/backup-disaster-recovery/
1Skills CLI (Vercel)
npx skills add aj-geddes/useful-ai-prompts --skill backup-disaster-recovery -a codex2Manually: put the files in place
.agents/skills/backup-disaster-recovery/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add aj-geddes/useful-ai-prompts --skill backup-disaster-recovery -a cursor2Manually: put the files in place
.cursor/skills/backup-disaster-recovery/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install aj-geddes/useful-ai-prompts backup-disaster-recovery2Manually: put the files in place
.github/skills/backup-disaster-recovery/SKILL.md1Skills CLI (Vercel)
npx skills add aj-geddes/useful-ai-prompts --skill backup-disaster-recovery -a gemini-cli2Platform CLI
gemini skills install https://github.com/aj-geddes/useful-ai-prompts --path skills/backup-disaster-recoveryManually: put the files in place
.devin/skills/backup-disaster-recovery/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add aj-geddes/useful-ai-prompts --skill backup-disaster-recovery -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about backup-disaster-recovery
How do I install backup-disaster-recovery in Claude?
Run npx skills add aj-geddes/useful-ai-prompts --skill backup-disaster-recovery -a claude-code. The skill file then lands at ~/.claude/skills/backup-disaster-recovery/SKILL.md.
What does backup-disaster-recovery do?
It guides the agent through backup strategies, disaster recovery plans and data restoration procedures, including cross-region failover.
What is inside the skill?
A short PostgreSQL backup cronjob example plus four guides in references/: database backup configuration, a disaster recovery plan template, a backup and restore script, and cross-region failover.
Source text
SKILL.md · MIT
---
name: backup-disaster-recovery
description: >
Implement backup strategies, disaster recovery plans, and data restoration
procedures for protecting critical infrastructure and data.
---
# Backup and Disaster Recovery
## Table of Contents
- [Overview](#overview)
- [When to Use](#when-to-use)
- [Quick Start](#quick-start)
- [Reference Guides](#reference-guides)
- [Best Practices](#best-practices)
## Overview
Design and implement comprehensive backup and disaster recovery strategies to ensure data protection, business continuity, and rapid recovery from infrastructure failures.
## When to Use
- Data protection and compliance
- Business continuity planning
- Disaster recovery planning
- Point-in-time recovery
- Cross-region failover
- Data migration
- Compliance and audit requirements
- Recovery time objective (RTO) optimization
## Quick Start
Minimal working example:
```yaml
# postgres-backup-cronjob.yaml
apiVersion: v1
kind: ConfigMap
metadata:
name: backup-script
namespace: databases
data:
backup.sh: |
#!/bin/bash
set -euo pipefail
BACKUP_DIR="/backups/postgresql"
RETENTION_DAYS=30
DB_HOST="${POSTGRES_HOST}"
DB_PORT="${POSTGRES_PORT:-5432}"
DB_USER="${POSTGRES_USER}"
DB_PASSWORD="${POSTGRES_PASSWORD}"
export PGPASSWORD="$DB_PASSWORD"
# Create backup directory
mkdir -p "$BACKUP_DIR"
# Full backup
BACKUP_FILE="$BACKUP_DIR/full-$(date +%Y%m%d-%H%M%S).sql"
// ... (see reference guides for full implementation)
```
## Reference Guides
Detailed implementations in the `references/` directory:
| Guide | Contents |
|---|---|
| [Database Backup Configuration](references/database-backup-configuration.md) | Database Backup Configuration |
| [Disaster Recovery Plan Template](references/disaster-recovery-plan-template.md) | Disaster Recovery Plan Template |
| [Backup and Restore Script](references/backup-and-restore-script.md) | Backup and Restore Script |
| [Cross-Region Failover](references/cross-region-failover.md) | Cross-Region Failover |
## Best Practices
### ✅ DO
- Perform regular backup testing
- Use multiple backup locations
- Implement automated backups
- Document recovery procedures
- Test failover procedures regularly
- Monitor backup completion
- Use immutable backups
- Encrypt backups at rest and in transit
### ❌ DON'T
- Rely on a single backup location
- Ignore backup failures
- Store backups with production data
- Skip testing recovery procedures
- Over-compress backups beyond recovery speed needs
- Forget to verify backup integrity
- Store encryption keys with backups
- Assume backups are automatically working
© aj-geddes · MIT · aj-geddes/useful-ai-prompts