BD huo15-flow-chart
2026 现代美学的流程图、泳道图、系统架构图、C4 架构图、时序图、状态图、ER 图、甘特图生成。Linear/Vercel/Radix 配色 + 软阴影 + 圆角 + 判断色强调 + 容器分层。输入 YAML/JSON 规格或 Mermaid/PlantUML/DOT 源码,输出 SVG/PNG/PDF/draw.io;PDF 默认单页自适应画布不分页;内置 17 种风格(含 v1.4 新增 editorial NYT 杂志 / bauhaus 红黄蓝几何 / swiss 国际主义 Helvetica 网格 三个有性格风格);支持 draw.io 源文件 + C4-PlantUML + 架构 Tier 分层。触发词:流程图、泳道图、时序图、状态图、ER 图、系统架构图、C4 图、画流程图、生成流程图、编辑杂志风、纽约客、NYT、Monocle、包豪斯、三原色、瑞士国际主义、Helvetica 网格、Müller-Brockmann。
As a process D 42/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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
-
low Dangerous commands
cmd-privilegescripts/flowchart_render.py:129Privilege escalation / world-writable permissions (detector / deny-list definition; string literal in code, not executed)pup_cfg.write_text(json.dumps({"args": ["--no-sandbox", "--disable-setuid-sandbox"]}))detectorcode literal
Files scanned: 19. 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") - note
frontmatter-keyunknown frontmatter key "displayName" - note
frontmatter-keyunknown frontmatter key "aliases" - note
frontmatter-keyunknown frontmatter key "dependencies"
Process rating: all ten parameters 42/100
- 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
- 60Tools and files. Uses tools (bash, python, node) that frontmatter does not declare
- 70Execution cost. Instruction body is 4662 tokens
- 100Steps. 88 steps
- 100Consistency. Name and required fields are in place
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
- -260 emoji in the instructions: noise for the model
- -32 of 5 scripts are never mentioned in SKILL.md
- +2Single-language instructions
- +3Description length 424: enough signal without eating the budget
- +4Structure: 23 headings
- +3Step-by-step instructions: 88 items
- +4Has examples (14 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 65.