diagram-maker

Create SVG/HTML or Excalidraw diagrams for concepts, architecture, flows, and whiteboards.

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/diagram-maker/SKILL.md

Quality

Content

72%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is concise, well-structured, and uses progressive disclosure effectively with real one-level reference files. It is held back by a weak, hedged validation step with no feedback loop and by deferring executable code to references rather than providing copy-paste-ready examples in-body.

Suggestions

Strengthen the workflow's verification step: replace 'when feasible' with a concrete parse/open command and add a validate-fix-retry loop for malformed output.

Include at least one minimal copy-paste-ready SVG/HTML or Excalidraw snippet inline so the skill is executable without opening the reference files.

Remove the tangential 'PilotDeck Migration Note' section, which is review metadata that does not aid the diagram-generation task.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence, with no explanation of what SVG/Excalidraw are; every line is actionable guidance (e.g., 'No external fonts, JS, images, gradients...').	3 / 3
Actionability	Provides precise field-level specs (e.g., 'Minimum labeled shape: 120x60', 'roughness 1, fontFamily: 1', 'Every connector path has fill="none"'), but includes no complete copy-paste-ready code in-body, deferring runnable snippets to reference files.	2 / 3
Workflow Clarity	A clear five-step numbered sequence exists, but the only validation step ('Verify syntax by opening/parsing when feasible') is hedged and lacks an explicit validate-fix-retry feedback loop.	2 / 3
Progressive Disclosure	Clear overview with well-signaled one-level-deep references to two real files (references/svg-template.md, references/excalidraw-patterns.md), with template and pattern content appropriately externalized.	3 / 3
	Total	10 / 12 Passed

Description

67%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific and distinctive, clearly conveying the diagramming niche and output formats. Its main weakness is the absence of explicit 'Use when...' trigger guidance, which leaves the 'when' only implied and caps completeness.

Suggestions

Add an explicit 'Use when...' clause naming concrete triggers (e.g., 'Use when creating architecture, flow, sequence, or whiteboard diagrams').

Broaden trigger term coverage to include natural variations users say, such as 'flowchart', 'sequence diagram', 'schematic', and 'chart'.

Dimension	Reasoning	Score
Specificity	Names two concrete output formats ('SVG/HTML or Excalidraw') and multiple diagram types (concepts, architecture, flows, whiteboards), listing several specific concrete actions rather than vague language.	3 / 3
Completeness	Clearly states what the skill produces, but provides no explicit 'Use when...' clause or trigger guidance, so the 'when' is only implied; the rubric caps completeness at 2 in that case.	2 / 3
Trigger Term Quality	Includes natural user terms like 'diagrams', 'architecture', 'flows', and 'whiteboards', but omits common variations such as 'flowchart', 'sequence diagram', 'chart', or 'schematic'.	2 / 3
Distinctiveness Conflict Risk	The named tools (SVG/HTML, Excalidraw) and specific output types carve out a clear diagramming niche unlikely to conflict with unrelated skills.	3 / 3
	Total	10 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: OpenBMB/PilotDeck
Path: skills/diagram-maker/SKILL.md
Commit: c88d7d1

Reviewed: about 13 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.