BF production-readiness
Define risk-scaled evidence packets and go/no-go/defer/exception launch gates with accountable owners. Do not use this skill for cross-domain production composition; use `production-excellence` for assembling migration, recovery, capacity, and incident evidence.
Define risk-scaled evidence packets and go/no-go/defer/exception launch gates with accountable owners.
As a process F 49/100 · Will not run — References files that are not bundled: ../release-engineering/SKILL.md, ../site-reliability-engineering/SKILL.md, ../secure-software-engineering/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 · 1
✓ No critical or high findings
Medium and low: 1
-
low Risky intent
intent-offensive-securitySKILL.md:48Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- **Security implementation, threat modeling, or penetration testing.** Route to
Files scanned: 4. 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: ../site-reliability-engineering/SKILL.md - warning
missing-refreference to a missing file: ../secure-software-engineering/SKILL.md - warning
missing-refreference to a missing file: ../security-audit-methodology/SKILL.md - warning
missing-refreference to a missing file: ../data-engineering/SKILL.md - warning
missing-refreference to a missing file: ../qa-methodology/SKILL.md - warning
missing-refreference to a missing file: ../platform-engineering/SKILL.md - warning
missing-refreference to a missing file: ../implementation-planning/SKILL.md - warning
missing-refreference to a missing file: ../spec-driven-development/SKILL.md - warning
missing-refreference to a missing file: ../verification-methodology/SKILL.md - warning
missing-refreference to a missing file: ../api-design-and-evolution/SKILL.md - warning
missing-refreference to a missing file: ../data-scientist/SKILL.md
Process rating: all ten parameters 49/100
- 0Tools and files. 12 referenced file(s) missing: ../release-engineering/SKILL.md, ../site-reliability-engineering/SKILL.md, ../secure-software-engineering/SKILL.md
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 2 mutating operations with no state check
- 40Result and completion. Does not say what the result is
- 50When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 100Steps. 26 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3084 tokens
- 100Progress reporting. Reports progress
- low 10 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (17 tags): a typed call is more reliable
- 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
- +4No input/output examples
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 262: enough signal without eating the budget
- +4Structure: 11 headings
- +3Step-by-step instructions: 26 items
- +4Reference files are cited in the instructions (2 of 2)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 77.