CtrlK
BlogDocsLog inGet started
Tessl Logo

excalidraw

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

64

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/creative/excalidraw/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

The body is lean, highly actionable, and well-structured: it gives complete JSON templates, concrete commands, a clear workflow, and offloads detail to verified one-level-deep reference files.

DimensionReasoningScore

Conciseness

The body is dense with Excalidraw-specific JSON details (container binding, fixedPoint coordinates, z-order, sizing) Claude does not already know, with no padding explaining what diagrams or libraries are, matching the 'lean and efficient; every token earns its place' anchor.

3 / 3

Actionability

It provides complete, copy-paste-ready element JSON templates and concrete commands like "python skills/diagramming/excalidraw/scripts/upload.py ~/diagrams/my_diagram.excalidraw", matching the 'fully executable code/commands; copy-paste ready' anchor.

3 / 3

Workflow Clarity

The Workflow section sequences write → save with write_file → optionally upload, and the simple-skill scoring note permits a 3 when the single task is unambiguous; diagram generation is not a destructive/batch operation requiring validation feedback loops.

3 / 3

Progressive Disclosure

Detailed material is split into clearly signaled one-level-deep references ("See references/colors.md", "see references/dark-mode.md", "see references/examples.md", scripts/upload.py), all of which exist on disk, matching the 'clear overview with well-signaled one-level-deep references' anchor.

3 / 3

Total

12

/

12

Passed

Description

57%

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 a concrete niche, but it is a terse noun phrase lacking explicit action verbs and any 'Use when…' trigger guidance, capping completeness and trigger coverage at 2.

Suggestions

Add explicit action verbs, e.g. 'Create and save hand-drawn Excalidraw JSON diagrams…'.

Append a 'Use when…' trigger clause naming user-facing terms like 'architecture, flowchart, or sequence diagrams'.

Spell out the abbreviated 'arch, flow, seq' as 'architecture, flowcharts, sequence diagrams' to match natural user phrasing.

DimensionReasoningScore

Specificity

"Hand-drawn Excalidraw JSON diagrams (arch, flow, seq)" names the domain and concrete diagram types but uses no action verbs (create/write/save), matching the 'names domain and some actions, but not comprehensive' anchor rather than the multi-action list required for 3.

2 / 3

Completeness

The description clearly states what the skill produces but has no 'Use when…' clause or equivalent trigger guidance, and the rubric explicitly caps completeness at 2 when that is missing.

2 / 3

Trigger Term Quality

"Excalidraw" and "diagrams" are natural user terms, but the abbreviated "arch, flow, seq" miss common full-word variations (architecture, flowchart, sequence) a user would actually say, fitting 'some relevant keywords but missing common variations' rather than full coverage.

2 / 3

Distinctiveness Conflict Risk

"Excalidraw" is a specific named tool giving a clear, distinct niche unlikely to trigger for other skills, matching the 'clear niche with distinct triggers' anchor rather than the generic-overlap anchor at 2.

3 / 3

Total

9

/

12

Passed

Validation

81%

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

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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
Reviewed

Table of Contents

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.