excalidraw

Generate hand-drawn style diagrams, flowcharts, and architecture diagrams as PNG images from Excalidraw JSON

Quality

73%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./public/skills/a-anand-91119/excalidraw/SKILL.md

Quality

Discovery

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 about capabilities and output format, creating a clear and distinctive niche around Excalidraw-based diagram generation. However, it lacks an explicit 'Use when...' clause which caps completeness, and could benefit from additional natural trigger terms users might use when requesting diagrams.

Suggestions

Add a 'Use when...' clause, e.g., 'Use when the user asks for diagrams, flowcharts, sketches, or visual architecture representations, or mentions Excalidraw.'

Include additional natural trigger terms like 'sketch', 'whiteboard diagram', 'visual diagram', 'drawing', or '.excalidraw' to improve keyword coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'hand-drawn style diagrams, flowcharts, and architecture diagrams' and specifies the output format (PNG images) and input format (Excalidraw JSON).	3 / 3
Completeness	Clearly answers 'what does this do' (generate hand-drawn style diagrams as PNG from Excalidraw JSON), but lacks an explicit 'Use when...' clause specifying when Claude should select this skill.	2 / 3
Trigger Term Quality	Includes good terms like 'diagrams', 'flowcharts', 'architecture diagrams', 'Excalidraw', and 'PNG', but misses common user variations like 'sketch', 'whiteboard', 'visual', 'drawing', or file extensions like '.excalidraw'.	2 / 3
Distinctiveness Conflict Risk	The combination of 'Excalidraw JSON', 'hand-drawn style', and 'PNG images' creates a very distinct niche that is unlikely to conflict with other diagramming or image generation skills.	3 / 3
	Total	10 / 12 Passed

Implementation

79%

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

This is a well-crafted skill with excellent actionability — the JSON examples are concrete, the arrow binding section is particularly well-documented with both simple and complex cases, and the color palette/layout guidelines provide useful reference data. The main weakness is the lack of validation steps in the workflow (e.g., checking render output, handling errors) and the content could benefit from splitting the template and detailed reference into separate files.

Suggestions

Add a validation/error-handling step after the render command (e.g., check if output PNG exists, handle render.js errors)

Consider moving the full flowchart template and color palette into a separate reference file to keep SKILL.md as a concise overview

Dimension	Reasoning	Score
Conciseness	The content is lean and efficient. Every section serves a purpose — element types table, arrow binding syntax, template, layout guidelines, and color palette are all reference material Claude wouldn't inherently know. No unnecessary explanations of what diagrams are or how rendering works.	3 / 3
Actionability	Provides fully executable JSON examples for arrows, shapes, and a complete flowchart template. The render command is concrete and copy-paste ready. Arrow binding examples cover both simple and multi-segment cases with specific JSON.	3 / 3
Workflow Clarity	The 4-step workflow is clearly sequenced, but there are no validation checkpoints — no step to verify the JSON is valid before rendering, no error handling if render.js fails, and no verification that the PNG was successfully created before sending. For a file generation workflow, this is a gap.	2 / 3
Progressive Disclosure	The content is well-organized with clear sections and a logical flow from workflow to reference to templates. However, the full flowchart template and detailed element reference could be split into separate files for a cleaner overview. For a skill of this length (~100 lines of content), it's borderline acceptable but slightly monolithic.	2 / 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: Demerzels-lab/elsamultiskillagent
Commit: f45fcb5

Reviewed: 12 days 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.