mermaid
Create diagrams and visualizations using Mermaid.js v11 syntax. Use when generating flowcharts, sequence diagrams, class diagrams, state diagrams, ER diagrams, Gantt charts, user journeys, timelines, or any of 24+ diagram types. Supports CLI rendering to SVG/PNG/PDF, theming, and configuration. Essential for inline documentation diagrams that render natively on GitHub.
95
93%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%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 is an excellent skill description that hits all the marks. It provides specific capabilities, comprehensive trigger terms covering many diagram types users might request, explicit 'Use when' guidance, and a clear niche around Mermaid.js that distinguishes it from other diagramming or visualization tools. The description is concise yet information-dense, using proper third-person voice throughout.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and capabilities: 'Create diagrams and visualizations', 'CLI rendering to SVG/PNG/PDF', 'theming', 'configuration', and enumerates specific diagram types like flowcharts, sequence diagrams, class diagrams, etc. | 3 / 3 |
Completeness | Clearly answers both 'what' (create diagrams using Mermaid.js v11, CLI rendering, theming, configuration) and 'when' with an explicit 'Use when...' clause listing specific diagram types and use cases like inline documentation diagrams for GitHub. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'Mermaid', 'flowcharts', 'sequence diagrams', 'class diagrams', 'state diagrams', 'ER diagrams', 'Gantt charts', 'user journeys', 'timelines', 'SVG', 'PNG', 'PDF', 'GitHub', 'diagrams', 'visualizations'. These are all terms users would naturally use when requesting diagram creation. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche: Mermaid.js specifically, v11 syntax, 24+ diagram types enumerated, and the GitHub rendering context. Unlikely to conflict with other visualization or diagramming skills due to the specific technology and format references. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill that efficiently covers Mermaid.js diagram creation with good actionability and excellent progressive disclosure. The main weakness is the lack of explicit validation/error-recovery workflows — particularly important since Mermaid syntax parsing failures are common and the skill itself mentions parse errors. The content is concise and respects Claude's intelligence throughout.
Suggestions
Add a validation workflow after the Syntax Rules section, e.g.: 'After creating a diagram: 1. Check for unclosed subgraphs 2. Verify node IDs don't use reserved words 3. Test with `mmdc -i diagram.mmd -o /dev/null` to catch parse errors before committing'
Include a brief troubleshooting pattern for common parse errors (e.g., missing `end` keyword, unquoted special characters) to create a feedback loop for error recovery
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It avoids explaining what Mermaid is in unnecessary detail, assumes Claude knows markdown and CLI tools, and every section delivers actionable information without padding. | 3 / 3 |
Actionability | Provides executable code blocks for inline markdown diagrams, CLI commands with real flags, and concrete syntax patterns. The flowchart example is copy-paste ready, and CLI commands include specific options like theme and background. | 3 / 3 |
Workflow Clarity | The skill covers diagram creation and CLI conversion but lacks explicit validation steps. There's no guidance on verifying diagram syntax correctness before committing, no error recovery workflow (e.g., what to do when parsing fails), and the complexity guideline (15+ elements) is mentioned but not integrated into a workflow. | 2 / 3 |
Progressive Disclosure | Excellent progressive disclosure with a clear overview in the main file and well-signaled one-level-deep references to 5 specific reference files. The WARNING callout about loading diagram-types.md only when needed is a particularly good touch for token efficiency. | 3 / 3 |
Total | 11 / 12 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 — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- tslateman/duet
- Commit
c3b1fc2
- 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.