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
Quality
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 essentially a placeholder that provides almost no useful information for skill selection. It lacks concrete actions, meaningful trigger terms, and explicit usage guidance. The only distinguishing element is the 'D2' name, but without explaining what D2 diagrams are or when to use this skill, Claude would struggle to select it appropriately.
Suggestions
Add specific capabilities like 'Creates D2 declarative diagrams including flowcharts, sequence diagrams, and architecture diagrams from text-based syntax'
Include a 'Use when...' clause with natural trigger terms: 'Use when the user asks for D2 diagrams, declarative diagrams, text-to-diagram conversion, or mentions .d2 files'
Remove duplicate trigger terms and add variations users would naturally say: 'd2', 'diagram code', 'declarative diagram', 'diagram markup'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only states 'D2 Diagram Creator' without listing any concrete actions. It doesn't explain what the skill actually does - no mention of creating, editing, exporting diagrams, or any specific capabilities. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and the 'when' guidance is just a duplicate trigger term. There's no explicit 'Use when...' clause or meaningful trigger guidance. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('d2 diagram creator' listed twice) and miss natural variations users would say like 'd2', 'diagram', 'flowchart', 'architecture diagram', '.d2 file', or 'create diagram'. | 1 / 3 |
Distinctiveness Conflict Risk | The 'D2' specification provides some distinctiveness from generic diagram tools, but 'Visual Content' category is vague and could overlap with other diagramming or visualization skills. | 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 a placeholder template with no actual D2-specific content. It contains only generic boilerplate describing what a skill should do rather than providing any actionable guidance on D2 diagram syntax, creation workflows, or examples. The content fails all dimensions by being verbose yet empty of substance.
Suggestions
Add executable D2 syntax examples showing basic shapes, connections, and styling (e.g., `shape: rectangle`, arrows, labels)
Include a concrete workflow: write .d2 file → render with `d2 input.d2 output.svg` → validate output
Remove all generic boilerplate ('provides automated assistance', 'follows industry best practices') and replace with D2-specific guidance
Add references to D2 documentation or example files for advanced features like layouts, themes, and animations
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about D2 diagrams. Phrases like 'provides automated assistance' and 'follows industry best practices' are filler that Claude doesn't need. | 1 / 3 |
Actionability | No concrete code, commands, or D2 syntax examples are provided. The skill describes what it does abstractly but gives zero executable guidance on how to actually create D2 diagrams. | 1 / 3 |
Workflow Clarity | No workflow or steps are defined. The content mentions 'step-by-step guidance' but provides none. There are no sequences, validation checkpoints, or actual process instructions. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic text with no references to detailed documentation, examples, or related files. No structure for discovery or navigation to deeper content. | 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
0c08951
- 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.