BF drawiodo
draw.io 自动做图 Skill。当用户要求画图、生成图表、做架构图、流程图、UML、ER 图、时序图、思维导图等时触发。生成 .drawio 文件并用 draw.io 打开。支持思考-确认-迭代-版本回溯的完整工作流，8 个 Hook Point 安全校验。
As a process F 33/100 · Will not run — References files that are not bundled: references/*.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 Edit
Files scanned: 38. 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/*.md - note
frontmatter-keyunknown frontmatter key "trigger" - note
frontmatter-keyunknown frontmatter key "trigger_negative" - note
frontmatter-keyunknown frontmatter key "sensitive_access" - note
frontmatter-keyunknown frontmatter key "critical_write" - note
frontmatter-keyunknown frontmatter key "permission_weight" - note
frontmatter-keyunknown frontmatter key "data_dir" - note
frontmatter-keyunknown frontmatter key "external_data_dir" - note
frontmatter-keyunknown frontmatter key "meta_field_sync" - note
frontmatter-keyunknown frontmatter key "faq_quality"
Process rating: all ten parameters 33/100
- 0Tools and files. 1 referenced file(s) missing: references/*.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. 1 mutating operations with no state check
- 100Steps. 45 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1690 tokens
- low 11 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
- -310 of 23 scripts are never mentioned in SKILL.md
- +2Single-language instructions
- +3Description length 132: enough signal without eating the budget
- +4Structure: 20 headings
- +3Step-by-step instructions: 45 items
- +4Has examples (6 code blocks)
- +4Reference files are cited in the instructions (12 of 12)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 65.