Set up a backup system that actually protects your photos, files, and devices — built on the 3-2-1 rule and, crucially, tested so it works when you need it.
SkillScore82Maintained
Automatic
◆DevOps & SRE pack
Last verified 8/31/2026
What it changes
Passed 18 of 22 test cases with the skill, and 12 of 22 without it.
Without skill55%
With skill82%
Checks it passed that the model alone missed
The response instructs performing an immediate single-file restore test.
The plan prioritizes camera photos over re-downloadable system ROMs and APKs.
The response provides the `zfs set compression=lz4` command for the dataset path.
and 4 more in the full report
7 fixed11 passed either way3 still failing1 broke
Pass-rate lift
+27 pp
Tokens
+2%
Agent turns
0%
Response time
-22%
Model gemini-3.6-flashMeasured 8/31/2026v118 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 7
Prompt
I am configuring a storage server with 6 x 4TB drives on FreeBSD. I want to construct a ZFS pool with double parity and create a dataset named 'datasets/db' with lz4 compression. Please provide the exact zpool and zfs command syntax to execute this.
What was checked, without and with the skill
Checked
Without skill
With skill
The response provides the `zpool create` command specifying `raidz2`.
Passed
Passed
The response provides the `zfs set compression=lz4` command for the dataset path.
Missed
Passed
case-20 · gemini-3.6-flash · 8/31/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md64 linessingle file
Backup Strategy
Everyone means to back up until the drive dies or the phone is lost. This builds a real system on the 3-2-1 rule — three copies, two media, one off-site — sized to your actual data and devices, automated so it happens on its own, and (the step everyone skips) tested by doing a restore, because an untested backup is just a hope.
What This Skill Produces
A 3-2-1 plan — three copies, on two types of media, with one off-site/cloud, mapped to your devices
Priorities — what to back up first (irreplaceable photos/documents) vs. what's re-downloadable
Automation — how to make backups run automatically so they don't depend on remembering
A restore test — actually recovering a file to prove the backup works
Resilience — protecting backups from ransomware/accidental-deletion and sync tools propagating a deletion to every copy (versioning, offline copy)
Required Inputs
Ask for these if not provided:
Devices & OS — computers, phones, and what platform each is
What matters most — photos, documents, work files, and roughly how much data
Current backups — what (if anything) exists now, and whether it's tested
Apply 3-2-1. Three copies, two different media (e.g. local drive + cloud), one off-site — so no single event (fire, theft, ransomware) takes everything.
Prioritize the irreplaceable. Photos, personal documents, and unique work first; apps and media you can re-download come later.
Automate it. Scheduled/continuous backup beats manual — the ones you have to remember are the ones that lapse.
Protect the backups themselves. Keep at least one copy offline or versioned, so ransomware or a bad sync-delete can't wipe every copy at once.
Test the restore. Recover a real file (and ideally a full-system test once). An untested backup fails exactly when it matters.
Audit the beneficiary designations that quietly override wills — the account-by-account sweep, the life-event triggers that make them stale, and the coordination check against actual intentions. Use when asked check my beneficiaries, does my 401k go to my ex, do beneficiary forms beat a will, or what should I update after marriage/divorce/a birth. Produces the account sweep list, the stale-designation red flags, the intent-vs-paperwork comparison table, and the update checklist with the verify-i