AB backup-strategy
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. Use when asked how to back up my data, set up backups, protect my photos/files, or what's a good backup strategy. Produces a 3-2-1 plan tailored to your devices and data, specific what-to-back-up priorities, an automation setup so it happens without you, a restore-test step, and protection against the failure that ruins backups (ransomware/sync-deletes reaching the backup).
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.
As a process B 67/100 · Nearly there — weak spots: when it triggers, failures and branches, running it twice
How to improve
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 5
✓ No critical or high findings
Medium and low: 5
-
low Risky intent
intent-offensive-securitySKILL.md:3Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (quoted — discussed, not commanded)description: "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. Use when asked how to back up
quoted -
low Risky intent
intent-offensive-securitySKILL.md:16Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- **Resilience** — protecting backups from ransomware/accidental-deletion and sync tools propagating a deletion to every copy (versioning, offline copy)
-
low Risky intent
intent-offensive-securitySKILL.md:25Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- **Threats of concern** — device loss/theft, hardware failure, ransomware, accidental deletion
-
low Risky intent
intent-offensive-securitySKILL.md:29Offensive-security / dual-use content (legitimate for authorised testing; review intended use)1. **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.
-
low Risky intent
intent-offensive-securitySKILL.md:32Offensive-security / dual-use content (legitimate for authorised testing; review intended use)4. **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.
Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 67/100
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 4 mutating operations with no state check
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Tools and files. No external tools needed
- 100Steps. 34 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 905 tokens
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +1No license
- +2Single-language instructions
- +3Description length 533: enough signal without eating the budget
- +4Structure: 9 headings
- +3Step-by-step instructions: 34 items
- +3Output format is stated explicitly
- +4Has examples (0 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 87.