BF skill-mermaid-diagrams
Generate consistent, template-based Mermaid diagrams for technical content. Supports 12 diagram types (architecture, flowchart, sequence, concept-map, radial-concept, timeline, comparison, comparison-table, gantt, mindmap, class-diagram, state-diagram) with automatic template selection, LLM-powered content generation, syntax validation, and error handling. Use when creating technical illustrations, system architecture visuals, project timelines, class diagrams, state machines, or documentation requiring uniform styling. Triggers on "mermaid diagram", "generate diagram", "create flowchart", "architecture diagram", "sequence diagram", "concept map", "gantt chart", "mind map", "class diagram", "UML diagram", "project timeline", "state diagram", "technical illustration".
Generate consistent, template-based Mermaid diagrams for technical content.
As a process F 62/100 · Will not run — References files that are not bundled: assets/*.mmd, assets/new-template.mmd
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 contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.
Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.
How to improve
- 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
-
medium Dangerous commands
cmd-shell-rcscripts/install-deps.sh:153Writes to a shell startup fileecho " echo 'export PATH=~/.npm-global/bin:\$PATH' >> ~/.bashrc"
-
medium Dangerous commands
cmd-shell-rcscripts/install-deps.sh:154Writes to a shell startup fileecho " source ~/.bashrc"
Files scanned: 23. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: assets/*.mmd - warning
missing-refreference to a missing file: assets/new-template.mmd
Process rating: all ten parameters 62/100
- 0Tools and files. 2 referenced file(s) missing: assets/*.mmd, assets/new-template.mmd
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 7 mutating operations with no state check
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 70Inputs and preconditions. Inputs and preconditions are listed
- 85Steps. 117 steps, 1 vague phrases
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3976 tokens
- low 16 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)
- -33 of 6 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +5Description quotes 13 example trigger phrases
- +3Description length 777: enough signal without eating the budget
- +4Structure: 31 headings
- +3Step-by-step instructions: 117 items
- +3Output format is stated explicitly
- +4Has examples (15 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.