d2-diagram-creator
D2 Diagram Creator - Auto-activating skill for Visual Content. Triggers on: d2 diagram creator, d2 diagram creator Part of the Visual Content skill category.
34
3%
Does it follow best practices?
Impact
87%
0.92xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/18-visual-content/d2-diagram-creator/SKILL.mdQuality
Discovery
7%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 description is extremely weak — it is essentially an auto-generated label with no substantive content. It fails to describe what the skill actually does, provides no natural trigger terms users would use, and lacks any explicit 'Use when...' guidance. The only slight positive is that 'D2' references a specific diagramming language, giving it minimal distinctiveness.
Suggestions
Add concrete actions the skill performs, e.g., 'Creates D2 diagrams from text descriptions, generates flowcharts, sequence diagrams, and architecture diagrams using D2 markup language.'
Add a 'Use when...' clause with natural trigger terms like 'Use when the user asks to create diagrams, flowcharts, sequence diagrams, entity-relationship diagrams, or mentions D2, .d2 files, or declarative diagramming.'
Include common user-facing keywords and file extensions such as 'diagram', 'flowchart', 'graph', 'architecture diagram', '.d2', 'visual layout' to improve trigger term coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the tool ('D2 Diagram Creator') but does not describe any concrete actions like creating diagrams, converting text to diagrams, editing layouts, etc. It is essentially a label with no actionable detail. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and the 'when' clause is just a redundant restatement of the skill name rather than explicit trigger guidance. There is no 'Use when...' clause with meaningful context. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'd2 diagram creator' repeated twice. There are no natural user keywords like 'diagram', 'flowchart', 'architecture diagram', 'graph', '.d2 file', or 'visual diagram' that users would actually say. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'D2' specifically (a particular diagramming language) provides some distinctiveness from generic diagramming tools, but the lack of detail about what it does versus other visual/diagram skills means overlap risk remains moderate. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty shell with no substantive content. It contains only auto-generated boilerplate that describes what a D2 diagram skill would do without actually teaching anything about D2 syntax, patterns, or usage. It provides no value to Claude beyond what it already knows.
Suggestions
Add concrete D2 syntax examples showing basic shapes, connections, and styling (e.g., `a -> b: connection label` with a complete diagram snippet).
Include a quick-start workflow: write D2 code → render with `d2 input.d2 output.svg` → validate output, with actual executable commands.
Replace the meta-description sections ('When to Use', 'Example Triggers', 'Capabilities') with actionable content like D2 layout options, theming, and common diagram patterns.
Add references to advanced topics (e.g., D2 classes, imports, sequence diagrams) either inline or via linked files for progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual D2 syntax, commands, or useful information. Every section restates the same vague idea. | 1 / 3 |
Actionability | There is zero concrete guidance—no D2 syntax examples, no executable code, no commands, no diagram snippets. The content describes rather than instructs, offering only vague promises like 'provides step-by-step guidance' without actually providing any. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The skill claims to provide 'step-by-step guidance' but contains no steps whatsoever. There are no validation checkpoints or sequenced instructions. | 1 / 3 |
Progressive Disclosure | The content is a flat, monolithic block of meta-descriptions with no references to detailed materials, no links to examples or advanced guides, and no meaningful structural organization beyond boilerplate headings. | 1 / 3 |
Total | 4 / 12 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.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
4dee593
- 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.