excalidraw
Use when working with *.excalidraw or *.excalidraw.json files, user mentions diagrams/flowcharts, or requests architecture visualization - delegates all Excalidraw operations to subagents to prevent context exhaustion from verbose JSON (single files: 4k-22k tokens, can exceed read limits)
88
83%
Does it follow best practices?
Impact
97%
1.59xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong description with excellent trigger terms and clear 'Use when' guidance. The main weakness is that it focuses more on implementation details (subagent delegation, token counts) rather than listing specific user-facing capabilities like creating, editing, or exporting diagrams.
Suggestions
Add specific concrete actions users can perform, e.g., 'Creates, edits, and exports Excalidraw diagrams and flowcharts' before the 'Use when' clause
Consider moving the implementation detail about subagents and token limits to the end or removing it, as it's less relevant for skill selection
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Excalidraw files, diagrams/flowcharts, architecture visualization) and mentions 'delegates operations to subagents', but doesn't list specific concrete actions like 'create diagrams', 'edit flowcharts', 'export visualizations'. | 2 / 3 |
Completeness | Explicitly answers both what (works with Excalidraw files, delegates to subagents) and when ('Use when working with *.excalidraw files, user mentions diagrams/flowcharts, or requests architecture visualization'). | 3 / 3 |
Trigger Term Quality | Includes excellent natural trigger terms: '*.excalidraw', '*.excalidraw.json', 'diagrams', 'flowcharts', 'architecture visualization' - these are terms users would naturally say when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Very distinct niche with specific file extensions (*.excalidraw, *.excalidraw.json) and clear domain focus on Excalidraw operations - unlikely to conflict with other diagramming or visualization skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill excels at actionability with concrete, executable task templates and clear workflow sequences for all Excalidraw operations. The core constraint (never read directly) is well-justified with real token data. However, the document is repetitive in reinforcing the same principle across multiple sections, and the length could be reduced by extracting detailed templates or analysis to separate files.
Suggestions
Consolidate the 'Common Rationalizations' table and 'Red Flags' section into a single reference, as they convey the same message
Consider extracting the detailed task templates to a separate TEMPLATES.md file, keeping only one example in the main skill
Remove the 'Why Straightforward JSON Doesn't Matter' section as it largely repeats points already made in 'The Problem' section
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is somewhat repetitive, restating the core principle ('never read directly, always delegate') multiple times across sections. The 'Common Rationalizations' table and 'Red Flags' section overlap significantly. However, the repetition serves a pedagogical purpose for a critical constraint, and the content avoids explaining concepts Claude already knows. | 2 / 3 |
Actionability | Provides concrete, copy-paste ready task templates for all four operation types (read, modify, create, compare). The templates include specific approach steps and expected return formats. The implementation example shows exact good vs bad patterns with clear task descriptions. | 3 / 3 |
Workflow Clarity | Each operation type has a clear numbered sequence with explicit steps. The modify and create templates include validation-like steps (find existing elements, confirm changes). The quick reference table provides unambiguous action-to-outcome mapping for all scenarios. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and tables, but it's a monolithic document (~200 lines) that could benefit from splitting detailed templates or token analysis into separate reference files. No external file references are provided for deeper dives. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
100%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
- softaworks/agent-toolkit
- Commit
3027f20
- 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.