BF software-dev-payload
软件开发领域负载物，覆盖软件全生命周期的12个子域、320个任务。涵盖需求工程、架构设计、编码实现、代码质量、测试验证、构建部署、运维监控、安全合规、工程效能、项目管理、技术文档、团队协作等全流程。高信息密度、高迭代性、高规范性。触发词：软件开发、需求工程、架构设计、编码实现、代码质量、测试验证、构建部署、运维监控、安全合规、工程效能、项目管理、技术文档、团队协作、meta-skill-system。
软件开发领域负载物，覆盖软件全生命周期的12个子域、320个任务。涵盖需求工程、架构设计、编码实现、代码质量、测试验证、构建部署、运维监控、安全合规、工程效能、项目管理、技术文档、团队协作等全流程。高信息密度、高迭代性、高规范性。触发词：软件开发、需求工程、架构设计、编码实现、代码质量、测试验证、构建部署、运维监控、…
As a process F 35/100 · Will not run — References files that are not bundled: references/software-dev-requirements.md
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- 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: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
missing-refreference to a missing file: references/software-dev-requirements.md
Process rating: all ten parameters 35/100
- 0Tools and files. 1 referenced file(s) missing: references/software-dev-requirements.md
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 100Steps. 38 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1035 tokens
- 100Running it twice. No mutating operations
- low 10 top-level sections: this looks like several domains in one skill
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
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 202: enough signal without eating the budget
- +4Structure: 22 headings
- +3Step-by-step instructions: 38 items
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (2 of 2)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 70.