agentleFS
nassaj2011nassaj2011/claude-skills-for-chatgpt/skills/backup-disaster-recovery/SKILL.md

backup-disaster-recovery

Skill0 starsChanged 27 days agoMITView on GitHub

Plan and verify backup integrity, isolated restore drills, RPO/RTO objectives, application consistency, provenance and incident recovery with explicit authorization.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use for backups, migrations, data-loss resilience, disaster recovery, ransomware recovery and continuity plans.

    line 9
  2. Distinctive:

    Check file-level checksum/catalogue manifests for tamper evidence, but separate integrity from restorability.

    line 15
  3. Distinctive:

    Never run an unapproved restore, expose backups with real personal data, claim encryption keys are recoverable without proof or …

    line 27

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Backup and disaster recovery — restore evidence over backup status

Trigger and safe boundary

Use for backups, migrations, data-loss resilience, disaster recovery, ransomware recovery and continuity plans. Nothing here authorizes restoring onto production or deleting retained backups. In ChatGPT Web with no filesystem tools, produce a runbook and label all verification NOT RUN.

Specialist recovery protocol

  1. Inventory critical data and dependencies: relational databases, files/object storage, key material (names only), WAL/PITR, worker queues, idempotency/payment state, DNS, runtime environment and third-party data. Identify system owners and blast radius.
  2. Agree RPO (acceptable data loss), RTO (acceptable downtime), testing cadence, retention/jurisdiction and incident priorities with accountable stakeholders. Missing targets are OPEN DECISIONS, not inferred numbers.
  3. Map backup type to consistency requirements: database-consistent dumps/snapshots, transaction logs, offsite/immutable copies, encrypted storage, key recovery, rotation and independent credentials. A list of backed-up files is not a database-consistent snapshot.
  4. Check file-level checksum/catalogue manifests for tamper evidence, but separate integrity from restorability. Review metadata, last success timestamp, storage reachability, encryption key access and coverage of tenant/application tables.
  5. Specify authorized isolated restore into a disposable environment, validate actor/tenant isolation, referential/financial integrity, queued job replay, payment side effects (disabled), health smoke and partial-failure recovery. Measure achieved restore time and point-in-time actual loss from controlled test markers.
  6. Perform negative fault drills only inside a disposable test: missing object, corrupted archive, stale key, incomplete WAL and restored backup with pending deletion requests. Record fail-closed decisions and protected originals.
  7. Release readiness requires actual restore evidence, responsible approval, measured RPO/RTO and known caveats. A backup dashboard showing green does not establish recovery.

Deliverables

Protection matrix | backup schedule/retention/key owner | restore checklist | measured vs target RTO/RPO | consistency and access tests | failures and remediation owner | declared readiness GO/NO-GO/NOT TESTED.

Executable reference

The repository provides scripts/backup_manifest.py for authorized backup-folder SHA-256 verification. A new examples/restore-drill/ synthetic source-to-isolated-destination drill tests exact content recovery, corruption detection and no-overwrite, but does not verify database consistency or production RTO. All tests create temporary data.

Hard limits

Never run an unapproved restore, expose backups with real personal data, claim encryption keys are recoverable without proof or automatically clean up user-owned originals.

Download now (ZIP)

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.