AF draw-io-diagram-generator
Use when creating, editing, or generating draw.io diagram files (.drawio, .drawio.svg, .drawio.png). Covers mxGraph XML authoring, shape libraries, style strings, flowcharts, system architecture, sequence diagrams, ER diagrams, UML class diagrams, network topology, layout strategy, the hediet.vscode-drawio VS Code extension, and the full agent workflow from request to a ready-to-open file.
io diagram files (.drawio, .drawio.svg, .drawio.png). Covers mxGraph XML authoring, shape libraries, style strings, flowcharts, system architecture, sequence…
As a process F 53/100 · Will not run — References files that are not bundled: assets/templates/flowchart.drawio, assets/templates/architecture.drawio, assets/templates/sequence.drawio
The same skill appears in 1 more place: RA-Skills
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 · 0
✓ No critical or high findings
Files scanned: 7. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: assets/templates/flowchart.drawio - warning
missing-refreference to a missing file: assets/templates/architecture.drawio - warning
missing-refreference to a missing file: assets/templates/sequence.drawio - warning
missing-refreference to a missing file: assets/templates/er-diagram.drawio - warning
missing-refreference to a missing file: assets/templates/uml-class.drawio - warning
missing-refreference to a missing file: assets/templates/
Process rating: all ten parameters 53/100
- 0Tools and files. 6 referenced file(s) missing: assets/templates/flowchart.drawio, assets/templates/architecture.drawio, assets/templates/sequence.drawio
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 1 mutating operations with no state check
- 60Result and completion. Output format stated, no completion criterion
- 60Failures and branches. 2 branches
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Execution cost. Instruction body is 4773 tokens
- 85Steps. 71 steps, 1 vague phrases
- 100Consistency. Name and required fields are in place
- 100Progress reporting. Reports progress
- low 11 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (13 tags): a typed call is more reliable
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)
- +1No license
- +2Single-language instructions
- +3Description length 392: enough signal without eating the budget
- +4Structure: 23 headings
- +3Step-by-step instructions: 71 items
- +3Output format is stated explicitly
- +4Has examples (12 code blocks)
- +4Reference files are cited in the instructions (3 of 3)
- +3All 2 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 82.