CtrlK
BlogDocsLog inGet started
Tessl Logo

excalidraw

Use when user requests diagrams, flowcharts, architecture charts, or visualizations. Also use proactively when explaining systems with 3+ components, complex data flows, or relationships that benefit from visual representation. Generates .excalidraw files and exports to PNG/SVG via Kroki API or locally using excalidraw-brute-export-cli.

68

Quality

85%

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

SKILL.md
Quality
Evals
Security

Quality

Content

78%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 content is highly actionable and well-sequenced with verification checkpoints, but it overloads SKILL.md by inlining reference material that belongs in separate files, and it fails to point at the bundled example assets that would aid progressive disclosure.

Suggestions

Split the long reference material (Diagram Patterns, Excalidraw JSON Structure, Common Mistakes) into separate files under references/ and link to them from SKILL.md, keeping the body as an overview.

Reference the bundled assets in the body — e.g., add an 'Example' section linking to assets/microservices-example.excalidraw and its PNG so users can study a working diagram.

Add an explicit validation checkpoint after the Export step (verify the output file exists and is non-empty) to complete the feedback loop for fragile render operations.

DimensionReasoningScore

Conciseness

Mostly lean and efficient: dense reference tables (color palette, spacing, font hierarchy) and minimal concept padding. A few sections (e.g., duplicate export guidance already summarized in Overview) could be trimmed, keeping it just short of fully lean.

4 / 5

Actionability

Fully executable throughout: copy-paste bash install/export commands, complete JSON element snippets with required properties, and concrete sizing formulas (width = max(160, charCount * 9)) cover the common cases.

5 / 5

Workflow Clarity

Clear 5-step workflow plus a section-by-section construction procedure with an explicit final-pass verification ('verify all boundElements and startBinding/endBinding references'). A minor validation gap: the export step lacks an explicit check that the PNG/SVG was actually produced.

4 / 5

Progressive Disclosure

Sections are well-organized, but the body is monolithic — all reference material (patterns, JSON structure, anti-patterns) is inlined rather than split into one-level-deep reference files, and the provided bundle assets (microservices-example.excalidraw/.png) are never referenced in the body.

3 / 5

Total

16

/

20

Passed

Description

92%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 strong: third-person voice, concrete actions with named tools, explicit 'what' and 'when' clauses, and a distinct niche. Minor improvement possible by adding a few natural synonyms (draw, schematic, schema) to the trigger terms.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('Generates .excalidraw files', 'exports to PNG/SVG') plus the specific tools ('Kroki API', 'excalidraw-brute-export-cli'), giving comprehensive coverage of what the skill does.

5 / 5

Completeness

Clearly answers 'what' (generate .excalidraw + export PNG/SVG) and 'when' with concrete explicit trigger phrases ('Use when user requests...', 'Also use proactively when...').

5 / 5

Trigger Term Quality

Strong keyword coverage ('diagrams, flowcharts, architecture charts, visualizations') plus explicit proactive triggers (3+ components, complex data flows), but missing common synonyms like 'draw' or 'schematic' that appear only in the body.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (Excalidraw diagrams specifically) with distinct file-format and tool triggers, making conflict with other skills minimal.

5 / 5

Total

19

/

20

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
dtsola/xiaoyaosearch
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.