BF restic
Install, configure, operate, secure, automate, tune, troubleshoot, and recover restic backups across local, SFTP, S3-compatible, cloud, and REST backends. Use when creating or managing a restic repository, designing backup or retention policy, validating restores, handling repository health or locks, moving repositories, or building safe scheduled backup jobs. Do not use for a generic file-copy task that does not need encrypted, deduplicated snapshots.
Install, configure, operate, secure, automate, tune, troubleshoot, and recover restic backups across local, SFTP, S3-compatible, cloud, and REST backends.
As a process F 39/100 · Will not run — References files that are not bundled: templates/backup-policy.env.example, templates/systemd/restic-backup.service, templates/systemd/restic-backup.timer
How to improve
- The text references files that are not there: add them or drop the references.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 3
✓ No critical or high findings
Medium and low: 3
-
low Risky intent
intent-offensive-securityreferences/security-and-threat-model.md:3Offensive-security / dual-use content (legitimate for authorised testing; review intended use)Use this reference whenever a task involves credentials, repository access, ransomware resistance, remote backends, or sharing recovery authority.
-
low Risky intent
intent-offensive-securityreferences/security-and-threat-model.md:22Offensive-security / dual-use content (legitimate for authorised testing; review intended use)| Endpoint ransomware | Separate credentials, least privilege, repository immutability/append-only options if appropriate, offline or independent copy |
-
low Risky intent
intent-offensive-securitySKILL.md:48Offensive-security / dual-use content (legitimate for authorised testing; review intended use)| Threat-model secrets, access, ransomware, or credentials | [security and threat model](references/security-and-threat-model.md) |
Files scanned: 16. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: templates/backup-policy.env.example - warning
missing-refreference to a missing file: templates/systemd/restic-backup.service - warning
missing-refreference to a missing file: templates/systemd/restic-backup.timer
Process rating: all ten parameters 39/100
- 0Tools and files. 3 referenced file(s) missing: templates/backup-policy.env.example, templates/systemd/restic-backup.service, templates/systemd/restic-backup.timer
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 4 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 85Steps. 14 steps, 1 vague phrases
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1639 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- medium 5 test cases, all positive: not one "should refuse" or "should ask first"
- low No test case covers injection arriving through data
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
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 456: enough signal without eating the budget
- +4Structure: 9 headings
- +3Step-by-step instructions: 14 items
- +4Has examples (2 code blocks)
- +4Reference files are cited in the instructions (9 of 9)
- +3All 4 scripts are documented
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.