BF excalidraw-diagram-generator
Generate Excalidraw diagrams from natural language descriptions. Use when asked to "create a diagram", "make a flowchart", "visualize a process", "draw a system architecture", "create a mind map", or "generate an Excalidraw file". Supports flowcharts, relationship diagrams, mind maps, and system architecture diagrams. Outputs .excalidraw JSON files that can be opened directly in Excalidraw.
As a process F 60/100 · Will not run — References files that are not bundled: templates/flowchart-template.json, templates/relationship-template.json, templates/mindmap-template.json
How to improve
- 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 · 0
✓ No critical or high findings
Files scanned: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 5813 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: templates/flowchart-template.json - warning
missing-refreference to a missing file: templates/relationship-template.json - warning
missing-refreference to a missing file: templates/mindmap-template.json - warning
missing-refreference to a missing file: scripts/split-excalidraw-library.py - warning
missing-refreference to a missing file: scripts/README.md - warning
missing-refreference to a missing file: scripts/.gitignore
Process rating: all ten parameters 60/100
- 0Tools and files. 6 referenced file(s) missing: templates/flowchart-template.json, templates/relationship-template.json, templates/mindmap-template.json
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Execution cost. Instruction body is 5813 tokens
- 100Steps. 200 steps
- 100Failures and branches. 2 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Running it twice. Mutating operations check current state
- low 13 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)
- -223 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +5Description quotes 6 example trigger phrases
- +3Description length 393: enough signal without eating the budget
- +4Structure: 35 headings
- +3Step-by-step instructions: 200 items
- +3Output format is stated explicitly
- +4Has examples (22 code blocks)
- +4Reference files are cited in the instructions (2 of 2)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.