BF release-engineering
Design, automate, and operate end-to-end software releases: release process models and pipelines (trunk-based development, CD stages, release trains), progressive delivery and feature flags, versioning and artifact management (SemVer, conventional commits, changelogs, SBOM/provenance), readiness and quality gates, rollback and recovery planning, change-management and audit compliance (SOC 2, SOX, PCI), DORA metrics, and multi-team release coordination. Do not use for application feature implementation (backend-engineering/frontend-engineering), production incident root-cause debugging or on-call/SLO operations (systematic-debugging / site-reliability-engineering), security implementation or threat modeling (secure-software-engineering), or internal developer platform construction (platform-engineering).
Design, automate, and operate end-to-end software releases: release process models and pipelines (trunk-based development, CD stages, release trains)…
As a process F 49/100 · Will not run — References files that are not bundled: ../backend-engineering/SKILL.md, ../frontend-engineering/SKILL.md, ../systematic-debugging/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 · 0
✓ No critical or high findings
Files scanned: 33. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ../backend-engineering/SKILL.md - warning
missing-refreference to a missing file: ../frontend-engineering/SKILL.md - warning
missing-refreference to a missing file: ../systematic-debugging/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: ../platform-engineering/SKILL.md - warning
missing-refreference to a missing file: ../data-engineering/SKILL.md - warning
missing-refreference to a missing file: ../spec-driven-development/SKILL.md - warning
missing-refreference to a missing file: ../api-design-and-evolution/SKILL.md - warning
missing-refreference to a missing file: ../verification-methodology/SKILL.md - warning
missing-refreference to a missing file: ../qa-methodology/SKILL.md - warning
missing-refreference to a missing file: ../agent-evals-and-observability/SKILL.md
Process rating: all ten parameters 49/100
- 0Tools and files. 12 referenced file(s) missing: ../backend-engineering/SKILL.md, ../frontend-engineering/SKILL.md, ../systematic-debugging/SKILL.md
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 25 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. 31 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3537 tokens
- 100Progress reporting. Reports progress
- 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
- +3Description length 814: 120–800 characters recommended
- +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
- +4Structure: 9 headings
- +3Step-by-step instructions: 31 items
- +4Reference files are cited in the instructions (15 of 15)
- +3All 5 scripts are documented
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 77.