excalidraw

Hand-drawn Excalidraw JSON diagrams (arch, flow, seq).

Quality

67%

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/creative/excalidraw/SKILL.md

Quality

Content

86%Weight 40%Scale 1-5

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

The body is a lean, highly actionable reference for Excalidraw's JSON format with copy-paste examples for every element type and well-organized one-level-deep references. The main weakness is workflow_clarity, which lacks a small verification checkpoint before the optional upload step.

Dimension	Reasoning	Score
Conciseness	The body is dense and Excalidraw-specific (container binding, z-order emission, fixedPoint) with no padding of basics Claude already knows, but the intro line "No accounts, no API keys, no rendering libraries -- just JSON" and the trailing "and more" are mildly trimmable.	4 / 5
Actionability	Every element type has complete, copy-paste-ready JSON, plus a concrete envelope template, save path, and exact upload command (`python skills/creative/excalidraw/scripts/upload.py ...`) covering the common cases.	5 / 5
Workflow Clarity	The four-step workflow (load → write JSON → save with write_file → optionally upload) is concrete and unambiguous, and the skill is non-destructive so the validation cap does not apply; minor gaps are the missing check that `cryptography` is installed before upload and no JSON well-formedness check before save.	4 / 5
Progressive Disclosure	Well-signaled one-level-deep references to `references/colors.md`, `references/dark-mode.md`, `references/examples.md`, and `scripts/upload.py` (all real files), with the most-used info (quick color table, core element format) kept inline and the bulk (full palettes, large examples) split out, with no nested reference chains.	5 / 5
	Total	18 / 20 Passed

Description

48%Weight 40%Scale 1-5

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 distinctive and names its niche clearly, but it is a noun phrase with no action verbs and no explicit "when to use" trigger guidance. Adding a verb ("Create") and a "Use when..." clause would lift the weaker dimensions.

Suggestions

Lead with a concrete action verb, e.g. "Create hand-drawn Excalidraw JSON diagrams for architecture, flow, and sequence diagrams."

Add an explicit trigger clause: "Use when the user asks for Excalidraw diagrams, flowcharts, architecture or sequence diagrams, or .excalidraw files."

Expand the abbreviated "(arch, flow, seq)" to natural terms like "architecture, flowcharts, sequence diagrams" to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	"Hand-drawn Excalidraw JSON diagrams (arch, flow, seq)" names the domain and output subtypes but contains no action verb (e.g. create/generate/edit), so actions are minimal rather than the 1-2 concrete actions required for a 3.	2 / 5
Completeness	It clearly states the "what" (hand-drawn Excalidraw JSON diagrams) but has no "Use when..." clause or equivalent trigger guidance, which per the rubric caps completeness at 3.	3 / 5
Trigger Term Quality	"Excalidraw" and "diagrams" are relevant natural keywords, but the type list uses abbreviations ("arch, flow, seq") and omits common synonyms and full forms (flowcharts, sequence diagrams, schematics).	3 / 5
Distinctiveness Conflict Risk	"Excalidraw" is a specific tool name giving a clear niche with minimal conflict risk, but the generic word "diagrams" leaves minor overlap with other diagramming skills (mermaid, draw.io) when no tool is named.	4 / 5
	Total	12 / 20 Passed

Validation

81%

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 — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	13 / 16 Passed

Repository: NousResearch/hermes-agent
Path: skills/creative/excalidraw/SKILL.md
Commit: 2635035

Reviewed: 8 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.