BB implementing-immutable-backup-with-restic
Implements ransomware-resistant backups using restic with S3-compatible Object Lock (AWS S3, MinIO, Backblaze B2), automating backup creation, integrity checks via restic check --read-data, retention enforcement, and restore testing. Use when building immutable backup infrastructure, adding a WORM copy to a 3-2-1-1-0 strategy, or automating scheduled backup-verification workflows.
Implements ransomware-resistant backups using restic with S3-compatible Object Lock (AWS S3, MinIO, Backblaze B2), automating backup creation, integrity…
As a process B 65/100 · Nearly there — weak spots: 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 · 4
✓ No critical or high findings
Medium and low: 4
-
low Risky intent
intent-offensive-securitySKILL.md:3Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (quoted — discussed, not commanded)description: 'Implements ransomware-resistant backups using restic with S3-c…ble
quoted -
low Risky intent
intent-offensive-securitySKILL.md:11Offensive-security / dual-use content (legitimate for authorised testing; review intended use)subdomain: ransomware-defense
-
low Risky intent
intent-offensive-securitySKILL.md:16Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- ransomware
-
low Risky intent
intent-offensive-securitySKILL.md:48Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- Establishing ransomware-resistant backup infrastructure with cryptographic integrity verification
Files scanned: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "domain" - note
frontmatter-keyunknown frontmatter key "subdomain" - note
frontmatter-keyunknown frontmatter key "nist_ai_rmf" - note
frontmatter-keyunknown frontmatter key "atlas_techniques" - note
frontmatter-keyunknown frontmatter key "nist_csf" - note
frontmatter-keyunknown frontmatter key "mitre_attack"
Process rating: all ten parameters 65/100
- 0Failures and branches. Linear process with no failure handling
- 30Running it twice. 3 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (python) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 14 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 827 tokens
- 100Progress reporting. Reports progress
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
- -41 reference files, but SKILL.md never points to them: the model will not open them
- -31 of 1 scripts are never mentioned in SKILL.md
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 383: enough signal without eating the budget
- +4Structure: 11 headings
- +3Step-by-step instructions: 14 items
- +3Output format is stated explicitly
- +4Has examples (1 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 82.