mermaid-class-diagram-generator
Mermaid Class Diagram Generator - Auto-activating skill for Visual Content. Triggers on: mermaid class diagram generator, mermaid class diagram generator Part of the Visual Content skill category.
36
3%
Does it follow best practices?
Impact
100%
1.00xAverage 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/mermaid-class-diagram-generator/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 boilerplate template with the skill name inserted, providing almost no useful information for skill selection. It lacks concrete actions, meaningful trigger terms, and any 'when to use' guidance. The duplicate trigger term and generic category label suggest this was auto-generated without human refinement.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates Mermaid class diagrams showing classes, attributes, methods, and relationships (inheritance, composition, association) from code or specifications.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to visualize class hierarchies, create UML-style class diagrams, generate Mermaid classDiagram syntax, or diagram object-oriented relationships.'
Include natural keyword variations users might say: 'class diagram', 'UML diagram', 'mermaid classDiagram', 'object relationships', 'inheritance diagram', 'class hierarchy visualization'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain ('Mermaid Class Diagram') but does not describe any concrete actions. There are no specific capabilities listed like 'generates class diagrams from code', 'adds relationships, methods, attributes', etc. It only states it is a 'generator' without elaborating on what it actually does. | 1 / 3 |
Completeness | The 'what' is extremely weak (just 'generator' with no specifics), and the 'when' is missing entirely. There is no 'Use when...' clause or equivalent explicit trigger guidance. The description fails to answer either question meaningfully. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('mermaid class diagram generator, mermaid class diagram generator'). There are no natural user-language variations like 'class diagram', 'UML diagram', 'mermaid syntax', 'visualize classes', 'object relationships', or '.mmd' that users might actually say. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Mermaid Class Diagram' does narrow the scope somewhat compared to generic diagram or visualization skills. However, the vague 'Visual Content' category and lack of specific triggers could cause overlap with other Mermaid diagram skills (sequence, flowchart, etc.) or general diagramming 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 an empty template/placeholder with no actual instructional content. It repeatedly names the skill topic ('mermaid class diagram generator') without providing any Mermaid syntax, class diagram examples, best practices, or actionable guidance. It fails on every dimension because it contains zero substantive content.
Suggestions
Add concrete Mermaid class diagram syntax examples (e.g., `classDiagram` block with classes, relationships, methods, and attributes) that are copy-paste ready.
Include a quick-reference section covering Mermaid class relationship types (inheritance, composition, aggregation, association) with their arrow syntax (e.g., `<|--`, `*--`, `o--`, `-->`).
Provide at least one complete, executable example showing a multi-class diagram with annotations, visibility modifiers (+, -, #, ~), and common patterns.
Add a workflow for generating diagrams from existing code: e.g., 1) Identify classes and relationships, 2) Draft the Mermaid syntax, 3) Validate rendering, 4) Iterate on layout.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats the skill name excessively, and contains zero substantive information about how to actually generate Mermaid class diagrams. | 1 / 3 |
Actionability | There is no concrete guidance whatsoever—no Mermaid syntax, no code examples, no commands, no class diagram structure. Every section is vague and abstract, describing rather than instructing. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The skill claims to provide 'step-by-step guidance' but contains none. There are no validation checkpoints or any sequenced instructions. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic placeholder text with no references to supporting files, no structured navigation, and no meaningful organization of content across sections. | 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
3a2d27d
- 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.