BF dev-task
开发项目任务管理,支持版本化开发流程。当用户需要启动开发任务、创建新版本、管理项目版本文档时使用。每次启动开发任务必须向用户确认版本编号,按版本号管理代码、开发文档、需求文档、发布配置。严格执行版本归档纪律,封版必须立即归档完整代码和文档。
开发项目任务管理,支持版本化开发流程。当用户需要启动开发任务、创建新版本、管理项目版本文档时使用。每次启动开发任务必须向用户确认版本编号,按版本号管理代码、开发文档、需求文档、发布配置。严格执行版本归档纪律,封版必须立即归档完整代码和文档。
As a process F 33/100 · Will not run — References files that are not bundled: references/doc-templates/
ProcedureInfrastructureWriting and documentstype and topics are labelled automatically from the skill text
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.
For the model run — optional
- 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 · 2
✓ No critical or high findings
Medium and low: 2
-
low Exfiltration
read-dotenvreferences/DEPLOY.template.md:23Reads a .env filecp .env.example .env
-
low Dangerous commands
cmd-background-processreferences/DEPLOY.template.md:63Starts a background / autostarted processsystemctl enable project-name
Files scanned: 5. 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/doc-templates/
Process rating: all ten parameters 33/100
Will not run. References files that are not bundled: references/doc-templates/
- 0Tools and files. 1 referenced file(s) missing: references/doc-templates/
- 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
- 30Running it twice. 5 mutating operations with no state check
- 100Steps. 32 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1233 tokens
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
- -31 of 1 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 120: enough signal without eating the budget
- +4Structure: 27 headings
- +3Step-by-step instructions: 32 items
- +4Has examples (10 code blocks)
- +4Reference files are cited in the instructions (3 of 3)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 67.