BF shisan-xinuo-workflow
一句话定位：把任何工程任务强制按「三级跑道（L1 快速通道 / L2-S 短工作流 / L2-F 完整 9 步）+ L1/L2/L3 封闭清单速判 + 三模式」推进的可审计 Agent 工程纪律工作流，核心纪律可平台无关硬注入。适用：任何动手工程任务——编码/多文件/跨模块/修 bug/建组件/审查/用户点名按流程；不适用：纯聊天问答、单文件只读查询、与工程无关的对话。
一句话定位：把任何工程任务强制按「三级跑道（L1 快速通道 / L2-S 短工作流 / L2-F 完整 9 步）+ L1/L2/L3 封闭清单速判 + 三模式」推进的可审计 Agent 工程纪律工作流，核心纪律可平台无关硬注入。适用：任何动手工程任务——编码/多文件/跨模块/修…
As a process F 33/100 · Will not run — References files that are not bundled: scripts/install-skill.ps1, references/details
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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 · 2
✓ No critical or high findings
Medium and low: 2
-
low Dangerous commands
cmd-pipe-to-shellreferences/never-list.md:44Downloads and executes remote code from an unrecognised host (pipe to shell) (negated — the text forbids it)- 永不执行 `curl <url> | bash` 或从未验证 URL 拉取即执行。
negated
A further 1 matches are quotations in this security skill's documentation and are not counted as findings.
Files scanned: 33. 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
body-longSKILL.md body ≈ 7211 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: scripts/install-skill.ps1 - warning
missing-refreference to a missing file: references/details
Process rating: all ten parameters 33/100
- 0Tools and files. 2 referenced file(s) missing: scripts/install-skill.ps1, references/details
- 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
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 5 mutating operations with no state check
- 70Execution cost. Instruction body is 7211 tokens
- 100Steps. 93 steps
- 100Consistency. Name and required fields are in place
- 100Progress reporting. Reports progress
- low 14 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
- -5TODO / placeholder text left in the skill
- +2Single-language instructions
- +3Description length 186: enough signal without eating the budget
- +4Structure: 25 headings
- +3Step-by-step instructions: 93 items
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (10 of 10)
- +3All 1 scripts are documented
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 56.