CC validating-backup-integrity-for-recovery
Validates backup integrity through cryptographic hash verification, automated restore testing, corruption detection, and recoverability checks to confirm backups are reliable for disaster recovery and ransomware response. Use before relying on backups for recovery, when building post-backup validation pipelines, auditing backup infrastructure for compliance, or checking immutable/air-gapped backups for silent corruption or tampering.
Validates backup integrity through cryptographic hash verification, automated restore testing, corruption detection, and recoverability checks to confirm…
As a process C 55/100 · Has gaps — weak spots: result and completion, 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 · 10
✓ No critical or high findings
Medium and low: 10
-
low Risky intent
intent-offensive-securityreferences/api-reference.md:18Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (detector / deny-list definition)# Scan for ransomware artifacts in restored data
detector -
low Risky intent
intent-offensive-securityreferences/api-reference.md:19Offensive-security / dual-use content (legitimate for authorised testing; review intended use)python agent.py --ransomware-scan /restore-test
-
low Risky intent
intent-offensive-securityreferences/api-reference.md:99Offensive-security / dual-use content (legitimate for authorised testing; review intended use)| 7.8 - 8.0 | Encrypted or fully random data (ransomware indicator) |
-
low Risky intent
intent-offensive-securityreferences/api-reference.md:101Offensive-security / dual-use content (legitimate for authorised testing; review intended use)## Ransomware Scan Output
-
low Risky intent
intent-offensive-securityreferences/api-reference.md:117Offensive-security / dual-use content (legitimate for authorised testing; review intended use)## Known Ransomware Extensions Detected
-
low Risky intent
intent-offensive-securitySKILL.md:5Offensive-security / dual-use content (legitimate for authorised testing; review intended use)confirm backups are reliable for disaster recovery and ransomware response. Use
-
low Risky intent
intent-offensive-securitySKILL.md:60Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- Verifying backup integrity before relying on backups for ransomware recovery
-
low Risky intent
intent-offensive-securitySKILL.md:141Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (detector / deny-list definition)### Step 5: Detect Ransomware Artifacts in Backups
detector -
low Risky intent
intent-offensive-securitySKILL.md:143Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (detector / deny-list definition)Before trusting a backup for recovery, scan for ransomware indicators:
detector -
low Risky intent
intent-offensive-securitySKILL.md:146Offensive-security / dual-use content (legitimate for authorised testing; review intended use)# Check for common ransomware file extensions
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_csf" - note
frontmatter-keyunknown frontmatter key "mitre_attack" - note
frontmatter-keyunknown frontmatter key "mitre_f3"
Process rating: all ten parameters 55/100
- 0Result and completion. Does not say what the result is
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 2 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
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 20 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1612 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
- +3Output format is not stated: the model decides each time
- -41 reference files, but SKILL.md never points to them: the model will not open them
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 437: enough signal without eating the budget
- +4Structure: 14 headings
- +3Step-by-step instructions: 20 items
- +4Has examples (6 code blocks)
- +3All 1 scripts are documented
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 85.