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 title and category label with no substantive content. It fails to describe concrete capabilities, lacks natural trigger terms users would use, and provides no guidance on when Claude should select this skill. The duplicate trigger term suggests auto-generated boilerplate rather than a thoughtfully crafted description.
Suggestions
Add specific concrete actions such as 'Generates Mermaid class diagrams showing classes, attributes, methods, inheritance, composition, and other relationships from code or specifications.'
Include a 'Use when...' clause with explicit triggers like 'Use when the user asks for a class diagram, UML visualization, object-oriented design diagram, or mentions Mermaid class syntax.'
Add natural keyword variations users might say: 'class diagram', 'UML', 'object relationships', 'inheritance diagram', 'mermaid classDiagram', '.mmd class diagram'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain ('Mermaid Class Diagram') but describes no concrete actions. There are no specific capabilities listed like 'generates class diagrams from code', 'adds relationships, methods, attributes', etc. It merely states it is a 'generator' without elaborating on what it actually does. | 1 / 3 |
Completeness | The description barely answers 'what does this do' (generates mermaid class diagrams, implied by the name) and has no explicit 'when should Claude use it' clause. There is no 'Use when...' guidance, which per the rubric should cap completeness at 2 at best, but even the 'what' is essentially absent. | 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', or 'object-oriented diagram'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Mermaid Class Diagram' is somewhat specific and distinguishes it from general diagramming or other Mermaid diagram types (flowcharts, sequence diagrams). However, the vague 'Visual Content' category and lack of detailed triggers could cause overlap with other Mermaid or 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 content about Mermaid class diagrams. It contains no syntax examples, no concrete guidance, and no actionable information—just repeated meta-descriptions of what the skill claims to do. It would provide zero value to Claude when generating class diagrams.
Suggestions
Add concrete Mermaid class diagram syntax with at least one complete, copy-paste-ready example (e.g., classDiagram with classes, relationships, and methods)
Include a quick reference of Mermaid class diagram relationship types (inheritance, composition, aggregation, etc.) with their arrow syntax
Provide a step-by-step workflow: gather class info → define classes → add relationships → add methods/attributes → validate rendering
Remove all meta-description sections (When to Use, Example Triggers, Capabilities) and replace with actual instructional content
| 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 Mermaid class diagram syntax, examples, or useful information. Every section restates the same vague concept. | 1 / 3 |
Actionability | There is zero concrete guidance—no Mermaid syntax, no code examples, no commands, no class diagram patterns. The content only describes what the skill would do rather than actually doing it. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The bullet 'Provides step-by-step guidance' is a claim with no actual steps provided. There are no validation checkpoints or sequenced instructions. | 1 / 3 |
Progressive Disclosure | The content is a flat, repetitive set of sections with no references to detailed materials, no linked resources, and no meaningful structure beyond boilerplate headings that all say the same thing. | 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
b8a3b3e
- 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.