mermaid-er-diagram-creator
Mermaid Er Diagram Creator - Auto-activating skill for Visual Content. Triggers on: mermaid er diagram creator, mermaid er diagram creator Part of the Visual Content skill category.
36
3%
Does it follow best practices?
Impact
98%
1.01xAverage 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-er-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 extremely weak—it is essentially a repeated skill name with a category label and no substantive content. It lacks concrete actions, meaningful trigger terms, and any explicit guidance on when Claude should select this skill. It would be nearly indistinguishable from other diagramming or Mermaid-related skills in a multi-skill environment.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates Mermaid-syntax ER diagrams from entity and relationship descriptions, including defining primary keys, foreign keys, cardinality, and relationship types.'
Add a 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks for an entity-relationship diagram, ER diagram, database schema visualization, data model diagram, or mentions Mermaid ER syntax.'
Expand trigger terms to include natural variations users would say: 'ER diagram', 'entity relationship', 'database schema', 'data model', 'mermaid diagram', '.mmd', 'erDiagram'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain ('Mermaid Er Diagram Creator') but provides no concrete actions. There is no mention of what specific tasks it performs—e.g., generating ER diagrams, defining entities/relationships, exporting Mermaid syntax. It is essentially just a label repeated. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name and does not provide any explicit 'when to use' guidance. There is no 'Use when...' clause or equivalent trigger guidance. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('mermaid er diagram creator'). It misses natural user phrases like 'entity relationship diagram', 'ER diagram', 'database schema diagram', 'mermaid syntax', or 'data model visualization'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Mermaid Er Diagram' does narrow the scope to a specific type of diagram in a specific syntax, which provides some distinctiveness. However, the lack of detail means it could overlap with a general Mermaid diagramming skill or a general ER diagram skill. | 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 with no actual content about Mermaid ER diagrams. It contains only meta-descriptions of what it claims to do without any Mermaid syntax, examples, best practices, or actionable guidance. It provides zero value to Claude for creating ER diagrams.
Suggestions
Add actual Mermaid ER diagram syntax with a complete, executable example (e.g., `erDiagram CUSTOMER ||--o{ ORDER : places` with entity attributes)
Include a reference of relationship types and their Mermaid notation (e.g., ||--o{, }|--|{, etc.) with brief descriptions of cardinality
Provide 2-3 concrete examples of increasing complexity (simple two-entity, multi-entity with attributes, full schema) that Claude can adapt
Remove all the meta-description sections (Purpose, When to Use, Capabilities, Example Triggers) and replace with actionable content about ER diagram creation
| 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 ER diagram syntax, examples, or useful information. Every token is wasted on boilerplate. | 1 / 3 |
Actionability | There is zero concrete guidance—no Mermaid ER diagram syntax, no code examples, no commands, no actual instructions on how to create an ER diagram. It only describes itself rather than instructing. | 1 / 3 |
Workflow Clarity | No workflow is defined. The skill claims to provide 'step-by-step guidance' but contains no steps whatsoever. There are no sequences, validation checkpoints, or any procedural content. | 1 / 3 |
Progressive Disclosure | The content has section headers but they contain only generic boilerplate. There are no references to external files, no meaningful content organization, and no actual substance to disclose progressively. | 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
4dee593
- 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.