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
Subagent delegation for diagram analysis
No raw JSON in report
100%
100%
Component list present
100%
100%
Relationships described
100%
100%
Key insights included
100%
100%
Delegation mentioned in methodology
0%
100%
No direct read claim
0%
100%
Text-only summary format
100%
100%
No excalidraw file dump
100%
100%
Subagent return format followed
100%
100%
Delegation for single file
0%
100%
Subagent delegation for diagram modification
Delegation in process log
0%
100%
No raw JSON in process log
0%
83%
Confirmation of changes
100%
100%
Position reported
100%
100%
Element IDs reported
100%
100%
No direct JSON editing claim
0%
100%
Modify template structure followed
0%
100%
No excalidraw dump in outputs
100%
100%
Connection arrows mentioned
100%
100%
Delegation for single-file modification
0%
100%
Subagent delegation for multi-diagram comparison
No raw JSON in comparison
100%
100%
Delegation mentioned for both files
0%
80%
Key architectural differences
100%
100%
Unique components listed
100%
100%
Relationship/flow differences
100%
100%
No full element details
100%
100%
No direct load of both diagrams
40%
100%
Text-based comparison format
100%
100%
Compare template structure
100%
100%
Isolated subagent calls
0%
42%
3027f20
Table of Contents
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.