excalidraw-diagram

基于文字说明或结构信息，生成可直接在 Excalidraw 中打开的手绘风 `.excalidraw` 图表；支持系统架构图、流程图、数据结构图与自由白板草图，输出标准 Excalidraw JSON。

Quality

62%

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

Quality

Content

57%

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

The body is well-structured and rich in Excalidraw-specific conventions, with a clear generation workflow and output spec. Its weaknesses are the absence of a complete executable JSON example and of any JSON validation step in the workflow.

Suggestions

Add a minimal complete, valid .excalidraw JSON example (or a small template with one node and one arrow) so the output is copy-paste ready rather than only structurally described.

Insert an explicit validation checkpoint in 生成规则 or 输出格式 — e.g. 'verify the JSON parses and every element id is unique before emitting Part 2'.

Tighten or trim restated guidance (the 使用时机 section and hedging phrases like '不追求复杂自动排版，只需给出合理、可读的初始位置') to improve token efficiency.

Dimension	Reasoning	Score
Conciseness	Most content covers Excalidraw-specific conventions Claude does not already know (element types, color hex codes, file structure fields), but phrases like '不追求复杂自动排版，只需给出合理、可读的初始位置' and the restated 使用时机 section could be tightened.	2 / 3
Actionability	It gives concrete field names and values (backgroundColor, strokeColor #1e1e1e, groupIds, type/version/source/elements/appState/files), but provides no complete, copy-paste-ready .excalidraw JSON example — only a structural description — leaving a key executable detail missing.	2 / 3
Workflow Clarity	The 生成规则 steps (解析→布局→元素生成→文件结构) and the two-part output format form a clear sequence, but there is no validation checkpoint confirming the generated JSON parses correctly, despite the skill emphasizing correct JSON syntax.	2 / 3
Progressive Disclosure	No bundle files exist and none are needed; the single-file body is organized into clearly labeled sections (使用时机, 支持图类型, 输入格式, 生成规则, 输出格式, 注意事项, 参考资源) with nothing that requires splitting into separate references.	3 / 3
	Total	9 / 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 stating what the skill produces and the diagram types it supports. Its main weakness is the absence of an explicit 'when to use' trigger clause and the lack of common natural phrasings users would actually say.

Suggestions

Add a 'Use when…' clause stating when Claude should invoke this skill (e.g. 'Use when the user asks to draw an architecture/flowchart/data-structure diagram or requests an Excalidraw diagram').

Include natural trigger phrasings users would say, such as '画个架构图', '画流程图', '画模块关系图', alongside the diagram-type keywords.

The what/when split is otherwise strong — keep the concrete action list and diagram-type enumeration as-is.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — '生成…图表', '输出标准 Excalidraw JSON' — and enumerates four specific diagram types (系统架构图、流程图、数据结构图、自由白板草图), matching the anchor for listing multiple specific concrete actions.	3 / 3
Completeness	It clearly answers 'what' (generate hand-drawn Excalidraw diagrams, output standard JSON), but there is no 'Use when…' clause or equivalent explicit trigger guidance, which caps completeness at 2 per the judging guidelines.	2 / 3
Trigger Term Quality	Names the diagram types and 'Excalidraw', which are relevant keywords, but omits natural user phrasings like '画个图' or '画流程图'; coverage is partial rather than comprehensive.	2 / 3
Distinctiveness Conflict Risk	The focus on native, directly-openable .excalidraw JSON gives it a clear niche unlikely to trigger for other skills; the named diagram types reinforce distinctiveness.	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: xstongxue/best-skills
Path: skills/excalidraw-diagram/SKILL.md
Commit: fd28854

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