CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

diagram-design

Create branded architecture, architecture delta, IT current-state, flowchart, sequence, state machine, ER/data model, timeline, swimlane, quadrant, radar/spider, polar chart (polar/radial lollipop), loop/flywheel, nested, tree, org chart, layer stack, exploded axonometric, axonometric plan, Venn, pyramid/funnel, treemap and marimekko, heatmap, bar and dumbbell, waterfall, line (slopegraph, ridgeline, streamgraph, bump), Gantt and scatter charts (bubble, beeswarm), high-level, process, medallion, data flow, DP integration, DP security matrix, Sankey, fishbone, Wardley map, kanban, user journey, service blueprint, deployment, dependency graph, UML class, story map, or database schema diagrams as HTML/SVG/PNG, with .drawio, Mermaid, and .excalidraw import, plus lifecycle phase maps, block decomposition trees, and onboarding guidance.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Failed to scan

The risk profile of this skill

The canonical home for this skill is diagram-design in cathrynlavery/diagram-design

SKILL.md
Quality
Evals
Security

Quality

Content

85%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.

A well-engineered overview: the body carries only selection logic, budgets, and rules, with all detail correctly pushed one level deep into 60+ verified reference files, and workflows (create, import, export) are explicitly gated by checklists and runnable verification scripts. The main deductions are deliberate cross-referenced repetition across §4/§6/§9 and two verification scripts (verify-geometry.py, verify-motion.py) that are referenced but absent from this bundle.

Suggestions

Ship scripts/verify-geometry.py and scripts/verify-motion.py in the bundle (or fold their checks into self_check.py) so the §6/§9 verification commands are runnable from the installed skill, not only a repository checkout

Replace the §4 anti-patterns row that restates the six connector rules (and the item-by-item §9 restatement) with pure rule-number back-references, e.g. 'Any breach of §6 rules 1–6'

Rewrite §0's gate paragraph as a small decision table (marker present / profile header / custom tokens / all defaults → action) to cut its dense conditional prose

DimensionReasoningScore

Conciseness

The body is dense and rule-driven — tables, exact thresholds, and routing logic with no explanation of concepts Claude already knows (it never explains what a Sankey or state machine is). Minor over-explanation/replication exists: the six §6 connector rules are restated in the §4 anti-patterns table and re-listed item-by-item in the §9 checklist, typography rules appear in both §5 and §9, and §0's gate prose is convoluted (long compound sentences about marker/header/default states). Fits anchor 4 ('minor instances ... could be trimmed'), not 5 ('every token earns its place').

4 / 5

Actionability

Highly concrete for an instruction-only skill: runnable commands ('python3 scripts/self_check.py <file>', 'python3 scripts/drawio_extract.py <input>'), exact geometry values (r=8 elbows, 12px attach-point spacing, dashed 5,4, rx=6, 4px grid), and a dial table with defaults. Minor gap: 'scripts/verify-geometry.py' and 'scripts/verify-motion.py' are invoked for verification but are not shipped anywhere in this bundle (only the six other scripts exist), so two checklist commands cannot actually be run from the installed skill. Fits anchor 4 ('concrete code or commands with minor gaps'), just short of anchor 5.

4 / 5

Workflow Clarity

Multi-step flows are clearly sequenced with explicit validation: §10's create-a-diagram steps (copy variant → choose pattern/type → replace → run the §9 taste gate), §11's import workflow (extract via script → set four dials → redraw → report fidelity ledger, with 'never invent ... never silently drop'), the §3 confirm-before-drawing checkpoint, and the §9 checklist acting as an explicit gate backed by runnable self-check scripts. This matches anchor 5: clear sequence, explicit validation steps, and checklist-based feedback for a complex process.

5 / 5

Progressive Disclosure

Scored against the actual bundle: every one of the ~60 reference paths cited in the body (45 type-*.md files, primitives/style-guide/onboarding/output-spec/layout-budget/import/export/animation/profiles) resolves to a real file, and asset template/example patterns exist. References are one level deep and well-signaled — each link states what the target owns ('That reference owns failures, the protected default, and save behavior'; 'Full text and edge cases: ...') — and the body keeps only thresholds and routing inline while detail lives in the references. Matches anchor 5 ('clear overview with well-signaled one-level-deep references ... easy navigation').

5 / 5

Total

18

/

20

Passed

Description

73%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.

An exhaustive, accurate trigger-term inventory with concrete output and import formats, undermined by a missing explicit 'Use when...' clause and heavy padding — the 45-type enumeration reads as a thesaurus dump rather than a description. It is distinguishable but invites overlap with generic charting skills on chart-type terms.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks for a diagram/architecture/flow diagram, wants a diagram made presentable, or provides .drawio/Mermaid/Excalidraw source to convert'

Compress the 45-type enumeration into grouped families (schematics, charts, maps/plans, UML/import) while keeping the highest-value trigger words, cutting roughly half the length

State the differentiator early — self-contained branded HTML/SVG editorial output — to reduce conflict with generic charting/dataviz skills

DimensionReasoningScore

Specificity

Concrete actions are present — 'Create branded ... diagrams as HTML/SVG/PNG, with .drawio, Mermaid, and .excalidraw import' — and domain coverage is exhaustive, but the action inventory is narrow (essentially create + import + 'onboarding guidance') while the bulk is a 45-item noun list, which the rubric's anti-verbosity guideline keeps out of anchor 5 ('Extract text and tables ..., fill forms, merge documents, convert pages' shows four distinct actions). Not anchor 3, since far more than 1–2 concrete actions and full output-format and import-format coverage are stated.

4 / 5

Completeness

The 'what' is clear and comprehensive, but there is no 'Use when...' clause or equivalent explicit trigger guidance — the rubric explicitly caps completeness at 3 for that. Not anchor 4 because the 'when' is entirely absent rather than just under-specified; the type names only weakly imply when.

3 / 5

Trigger Term Quality

Comprehensive natural-language coverage: every diagram name a user would actually say ('flowchart', 'sequence', 'state machine', 'Gantt', 'Sankey', 'Wardley map', 'UML class'), tool/source terms ('.drawio', 'Mermaid', '.excalidraw'), and synonyms ('radar/spider', 'loop/flywheel', 'slopegraph', 'treemap and marimekko'). Matches the anchor-5 example pattern of natural terms plus file extensions; nothing common is missing.

5 / 5

Distinctiveness Conflict Risk

A clear niche (editorial HTML/SVG/PNG diagram generation with import routes) with highly specific triggers, but generic chart types ('bar and dumbbell', 'line (slopegraph ...)', 'heatmap', 'Gantt and scatter') overlap with general charting/dataviz skills and the description doesn't state how it differs (self-contained editorial HTML vs. library-rendered charts). Not anchor 5 for that overlap; well above anchor 3's 'could still overlap with similar skills' since the vast majority of triggers are diagram-type-specific.

4 / 5

Total

16

/

20

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

anbeime/skill

Path

skills/diagram-design/skills/diagram-design/SKILL.md

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.