mcpField
B
backup-restore-design

backup-restore-design

github.com/sylphxaiCloud & DevOps153 installsUpdated today
Repository

About backup-restore-design

A skill for designing data durability as both a product capability and an operational system. It guides teams through backup, restore, security, and recovery testing, with runbooks and evidence as outputs.

Key features

  1. 01Classifies data types
  2. 02Defines RPO, RTO, and retention
  3. 03Plans backup and restore
  4. 04Designs conflict and migration handling
  5. 05Specifies recovery drills and evidence

Use cases

  1. 01Designing product backup and restore
  2. 02Setting recovery targets and retention
  3. 03Preparing verified recovery runbooks

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/sylphxai/skills --skill backup-restore-design

After installing, type/backup-restore-designin Claude Code to confirm it loaded.

Bundled filesagents/openai.yamlreferences/backup-restore-patterns.md

Details

From the project README

Backup Restore Design

Use this skill to design data durability as a product feature and operational system.

Workflow

  1. Identify data classes: user content, settings, purchases, game progress, files, account state, audit records, analytics, secrets.
  2. Read references/backup-restore-patterns.md.
  3. Define RPO/RTO, retention, encryption, ownership, export, deletion, and support visibility.
  4. Design backup, restore, conflict resolution, migration, and recovery drills.
  5. Prove restore works with procedural runbooks, checksum/manifest verification, evidence retention, owners, alerting, and cost/capacity guardrails.
  6. For E2EE products, keep plaintext and master keys client-owned; support may verify encrypted snapshot integrity and guide recovery, but must not hold or unwrap user content keys unless the product explicitly has an enterprise escrow model.
  7. Produce event schema and failure modes.

When not to use

  • Do not use for generic advice the base model already handles without this skill's specific artifact contract.

Guardrails

  • Do not promise durability without tested restore drills and checksum evidence.
  • Do not store secrets or master keys in backups unless encryption and access policy are explicit.
  • Do not design restore paths that bypass deletion, export, or privacy commitments.

Output format

Data classes:
Durability target:
RPO/RTO and retention:
Backup design:
Restore design:
Conflict handling:
Security/privacy:
Support/admin tooling:
Restore proof:
Failure modes:

Comments

Markdown supported