BF agile-workflow
全自动敏捷协作工作流引擎 v7.18.1 - 细纲串行+正文并行、并发安全架构、零数据污染、智能合并
As a process F 37/100 · Will not run — References files that are not bundled: /workspace/docs/agile-workflow-architecture.md, /workspace/docs/learning-system.md, /workspace/docs/troubleshooting.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.
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 Dangerous commands
cmd-cron-mentionSKILL.md:163Mentions editing / listing crontabcrontab -e
-
low Dangerous commands
cmd-background-processSKILL.md:434Starts a background / autostarted processnohup node agile-workflow-engine.js start > engine.log 2>&1 &
Files scanned: 80. 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: /workspace/docs/agile-workflow-architecture.md - warning
missing-refreference to a missing file: /workspace/docs/learning-system.md - warning
missing-refreference to a missing file: /workspace/docs/troubleshooting.md - warning
missing-refreference to a missing file: scripts/task-dependency-generator.js - warning
missing-refreference to a missing file: scripts/repair-task-states.js
Process rating: all ten parameters 37/100
Will not run. References files that are not bundled: /workspace/docs/agile-workflow-architecture.md, /workspace/docs/learning-system.md, /workspace/docs/troubleshooting.md
- 0Tools and files. 5 referenced file(s) missing: /workspace/docs/agile-workflow-architecture.md, /workspace/docs/learning-system.md, /workspace/docs/troubleshooting.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
- 20When it triggers. No condition that starts the skill
- 100Steps. 43 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2410 tokens
- 100Running it twice. No mutating operations
- 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)
- +3Description length 50: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- -4Absolute local paths (C:\Users, /home/…): not portable
- -269 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +4Structure: 51 headings
- +3Step-by-step instructions: 43 items
- +4Has examples (26 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 51.
External checks
ClawHub: suspicious
This workflow skill is not clearly malicious, but it can run persistent automation that starts, stops, restarts, and repairs local agents with limited user confirmation.
LLM: suspicious (high) · VirusTotal: · 29 May 2026