BF secure-software-engineering
Use when designing or implementing software securely: define security requirements, threat-model a feature, choose secure defaults, design authentication and authorization, handle untrusted data and secrets, evaluate dependencies, design multi-tenant trust boundaries, or review security-sensitive changes. Use for prevention during requirements, design, implementation, and review; not for post-build security assessments or scanning an existing codebase.
Use when designing or implementing software securely: define security requirements, threat-model a feature, choose secure defaults, design authentication and…
As a process F 47/100 · Will not run — References files that are not bundled: ../security-audit-methodology/SKILL.md, ../spec-driven-development/SKILL.md, ../verification-methodology/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: 17. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ../security-audit-methodology/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: ../multi-tenant-saas-architecture/SKILL.md - warning
missing-refreference to a missing file: ../capacity-and-cost-engineering/SKILL.md - warning
missing-refreference to a missing file: ../privacy-engineering/SKILL.md - warning
missing-refreference to a missing file: ../release-engineering/SKILL.md
Process rating: all ten parameters 47/100
- 0Tools and files. 7 referenced file(s) missing: ../security-audit-methodology/SKILL.md, ../spec-driven-development/SKILL.md, ../verification-methodology/SKILL.md
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 6 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. 9 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1557 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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 456: enough signal without eating the budget
- +4Structure: 8 headings
- +3Step-by-step instructions: 9 items
- +4Reference files are cited in the instructions (12 of 12)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 77.