What problem does it solve? Encrypted incremental backups are only as safe as the passphrase protecting them, and restores can silently fail or overwrite live data if handled carelessly. This Skill gives operators the safety rules for running incremental_backup and restore_from_backup without losing data or creating false confidence. ## Core Features & Use Cases - Passphrase Custody Guidance: Explains the scrypt-derived encryption key model and the absence of any recovery mechanism, so users understand that a lost passphrase means a permanently unrecoverable backup. - Backup Scope Rules: Identifies content that never needs backing up, such as open data already republished by public sources like the legal-kb MCP, avoiding wasted storage and upload time. - Restore Verification Checklist: Requires checking files_failed is empty before declaring success, treating manifest decrypt errors as loud stop signals, and using manifest_timestamp for point-in-time restores. - Use Case: A law firm enables nightly encrypted backups of client matter files; before trusting a restore after an accidental deletion, the operator restores an older manifest_timestamp into a separate target_path instead of overwriting /workspace. ## Quick Start Explain the passphrase risks and then walk me through restoring my encrypted backup to a separate target path without overwriting my current workspace.
