d2-diagram-creator
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill d2-diagram-creatorD2 Diagram Creator - Auto-activating skill for Visual Content. Triggers on: d2 diagram creator, d2 diagram creator Part of the Visual Content skill category.
Overall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely lacking in substance - it's essentially just a title with auto-generated metadata. It provides no information about what D2 diagrams are, what actions the skill can perform, or when Claude should select it. The duplicate trigger term suggests this may be a template that wasn't properly filled out.
Suggestions
Add specific capabilities: 'Creates D2 declarative diagrams including flowcharts, sequence diagrams, entity-relationship diagrams, and architecture visualizations from text-based syntax.'
Add explicit trigger guidance: 'Use when the user asks to create diagrams, visualize architecture, draw flowcharts, or mentions D2, .d2 files, or declarative diagramming.'
Include natural user terms in triggers: 'diagram', 'flowchart', 'architecture diagram', 'sequence diagram', 'visualize', 'draw', '.d2'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only states 'D2 Diagram Creator' without describing 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 provides no explicit 'when to use' guidance. The 'Triggers on' section is redundant and doesn't constitute proper usage guidance. | 1 / 3 |
Trigger Term Quality | The trigger terms listed are just 'd2 diagram creator' repeated twice. Missing natural user terms like 'diagram', 'flowchart', 'architecture diagram', 'visual', '.d2 files', or variations users would actually say. | 1 / 3 |
Distinctiveness Conflict Risk | The D2 format is somewhat specific and wouldn't conflict with general diagramming tools, but 'Visual Content' category is vague. Could potentially conflict with other diagram or visualization skills without clearer scope definition. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill content is essentially a placeholder template with no actual D2-specific information. It contains only generic boilerplate text that could apply to any skill, providing no executable code, no D2 syntax examples, no concrete guidance, and no useful information for creating D2 diagrams.
Suggestions
Add concrete D2 syntax examples showing basic shapes, connections, and styling (e.g., `shape: rectangle`, `a -> b: label`)
Include a complete, executable D2 diagram example that can be copy-pasted and rendered
Provide a quick-start workflow: write .d2 file -> render with `d2 input.d2 output.svg` -> validate output
Add references to D2-specific features like layouts, themes, and advanced styling with links to detailed documentation
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing Claude doesn't already know. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler with no actual D2-specific information. | 1 / 3 |
Actionability | There is zero concrete guidance - no D2 syntax, no code examples, no commands, no actual instructions on how to create D2 diagrams. The content describes rather than instructs. | 1 / 3 |
Workflow Clarity | No workflow is provided whatsoever. There are no steps for creating D2 diagrams, no validation checkpoints, and no process to follow. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic text with no references to detailed materials, no links to D2 documentation, examples, or advanced features. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
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.