BF site-reliability-engineering
Design, operate, and improve reliable production systems with SLOs, incident command, observability, error budgets, and operational practices. Do not use this skill for unrelated requests; route to the nearest named specialist.
Design, operate, and improve reliable production systems with SLOs, incident command, observability, error budgets, and operational practices.
As a process F 44/100 · Will not run — References files that are not bundled: ../release-engineering/SKILL.md, ../systematic-debugging/SKILL.md, ../telemetry/SKILL.md
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 · 2
✓ No critical or high findings
Medium and low: 2
-
low Dangerous commands
cmd-privilegetemplates/runbook-template.md:276Privilege escalation / world-writable permissions (detector / deny-list definition; documentation table row)| **Resolution** | 1. **Immediate:** `sudo journalctl --vacuum-size=500M` or `truncate -s0 /var/log/[app].log`<br>2. Clean old logs: `find /var/log -name "*.log.*" -mtime +7 -delete`<br>3. Clean temp
detectortable -
low Risky intent
intent-offensive-securitytemplates/service-review-checklist.md:189Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- [ ] [\_] A penetration test or security review has been completed (or is scheduled)
Files scanned: 36. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ../release-engineering/SKILL.md - warning
missing-refreference to a missing file: ../systematic-debugging/SKILL.md - warning
missing-refreference to a missing file: ../telemetry/SKILL.md - warning
missing-refreference to a missing file: ../grafana/SKILL.md
Process rating: all ten parameters 44/100
- 0Tools and files. 4 referenced file(s) missing: ../release-engineering/SKILL.md, ../systematic-debugging/SKILL.md, ../telemetry/SKILL.md
- 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
- 50When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 100Steps. 4 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2180 tokens
- 100Running it twice. No mutating operations
- medium 10 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
- +4No input/output examples
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 227: enough signal without eating the budget
- +4Structure: 8 headings
- +3Step-by-step instructions: 4 items
- +4Reference files are cited in the instructions (20 of 22)
- +3All 1 scripts are documented
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 80.