BF agent-sdd-bootstrap
［何时使用］当用户要为项目初始化 OpenSpec/SDD（Spec-Driven Development）工作流时；当用户说"配置 SDD""初始化 openspec""搭建 spec-driven 开发环境"时；当需要在 atomcode、zcode 等 OpenSpec 非原生支持的 Agent CLI 上接入 SDD 时
［何时使用］当用户要为项目初始化 OpenSpec/SDD（Spec-Driven Development）工作流时；当用户说"配置 SDD""初始化 openspec""搭建 spec-driven 开发环境"时；当需要在 atomcode、zcode 等 OpenSpec 非原生支持的 Agent CLI…
As a process F 33/100 · Will not run — References files that are not bundled: references/powershell.md
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.
Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.
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 · 1
✓ No critical or high findings
Medium and low: 1
-
medium Broad scope
meta-broad-allowed-toolsSKILL.md:1Broad tool permissions pre-approved: bashallowed-tools: bash read write glob grep
Files scanned: 0. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Unexpected scalar at node end at line 2, column 79: …/SDD（Spec-Driven Development）工作流时；当用户说"配置 SDD""初始化 openspec""搭建 spec-driven 开发… ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
missing-refreference to a missing file: references/powershell.md - note
frontmatter-keyunknown frontmatter key "skill_type" - note
frontmatter-keyunknown frontmatter key "created"
Process rating: all ten parameters 33/100
- 0Tools and files. 1 referenced file(s) missing: references/powershell.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
- 30Running it twice. 2 mutating operations with no state check
- 100Steps. 22 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1236 tokens
- low 13 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
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +5Description quotes 3 example trigger phrases
- +3Description length 165: enough signal without eating the budget
- +4Structure: 21 headings
- +3Step-by-step instructions: 22 items
- +4Has examples (11 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 60.