From backup-planner
Capture the user's available backup infrastructure (S3/B2/R2 buckets, rsync.net, NAS, external drives, existing restic repos, etc.) to persistent memory so it can be reused across projects without re-asking. Use when the user mentions backup destinations, or before evaluating backup options.
npx claudepluginhub danielrosehill/claude-code-plugins --plugin backup-plannerThis skill uses the workspace's default tool permissions.
The user likely has standing backup infrastructure — cloud object storage accounts, a home NAS, rsync.net quota, an existing restic/borg repo — that should be reused across every project rather than re-provisioned. Capture this once, then recall it for every future backup plan.
Conducts multi-round deep research on GitHub repos via API and web searches, generating markdown reports with executive summaries, timelines, metrics, and Mermaid diagrams.
Share bugs, ideas, or general feedback.
The user likely has standing backup infrastructure — cloud object storage accounts, a home NAS, rsync.net quota, an existing restic/borg repo — that should be reused across every project rather than re-provisioned. Capture this once, then recall it for every future backup plan.
Before resolving the data directory, check for legacy data at these paths:
~/.claude/projects/-home-*/memory/reference_backup_*.mdFor each legacy file that exists AND where <plugin-data-dir>/references/backup_<short-name>.md does NOT exist, move it to the new location (renamed without the reference_ prefix — e.g. reference_backup_b2.md → backup_b2.md) and delete the legacy file. Tell the user: "Migrated backup-destination reference files from ~/.claude/projects/.../memory/ to ."
Resolve the plugin's data directory as $CLAUDE_USER_DATA/backup-planner/ if CLAUDE_USER_DATA is set; otherwise $XDG_DATA_HOME/claude-plugins/backup-planner/ if XDG_DATA_HOME is set; otherwise ~/.local/share/claude-plugins/backup-planner/. Create the directory (and a references/ subdirectory) if it doesn't exist. See the canonical convention in the claude-rudder:plugin-data-storage skill.
<plugin-data-dir>/references/. Filename pattern: backup_<short-name>.md.---
name: Backup destination — <short name>
description: <provider, type, what it's good for>
type: reference
---
- **Type:** <S3-compatible / SSH / NAS / etc.>
- **Provider / Host:** <e.g. Backblaze B2, rsync.net, 10.0.0.x>
- **Capacity / quota:** <e.g. 1 TB provisioned, ~400 GB free>
- **Region:** <e.g. eu-central, on-prem Jerusalem>
- **Access:** <where credentials live — 1Password item name, env var, ~/.config/...>
- **Cost profile:** <flat / per-GB / egress-free / etc.>
- **Current use:** <empty / holds restic repo "foo" / shared with project X>
- **Notes:** <quirks, e.g. "B2 application key is restricted to bucket XYZ">
When starting evaluate-backup-options on a new project, read the <plugin-data-dir>/references/backup_*.md files first so recommendations draw from the real pool.