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
Quality
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 essentially a placeholder that only contains the skill name and category metadata. It lacks any substantive information about what the skill does, what actions it performs, or when Claude should select it. The duplicate trigger term suggests auto-generated content without human refinement.
Suggestions
Add specific actions the skill performs, e.g., 'Creates Mermaid ER diagrams showing entities, attributes, and relationships for database schema visualization.'
Include a 'Use when...' clause with natural trigger terms like 'ER diagram', 'entity relationship', 'database schema', 'ERD', 'data model visualization'.
Expand trigger terms to include variations users would naturally say: 'database diagram', 'table relationships', 'schema diagram', 'Mermaid ERD'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only states the skill name 'Mermaid Er Diagram Creator' without describing any concrete actions. There are no verbs or specific capabilities listed like 'creates entity-relationship diagrams' or 'generates database schemas'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and provides no 'when should Claude use it' guidance. There is no 'Use when...' clause or equivalent explicit trigger guidance. | 1 / 3 |
Trigger Term Quality | The triggers listed are just the skill name repeated twice ('mermaid er diagram creator'). Missing natural user terms like 'ER diagram', 'entity relationship', 'database diagram', 'schema visualization', or 'ERD'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Mermaid' and 'ER Diagram' provides some specificity that distinguishes it from generic diagram tools, but the lack of detail about capabilities 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 essentially a placeholder template with no actual instructional content. It describes capabilities it doesn't deliver and provides no Mermaid ER diagram syntax, examples, or actionable guidance. The entire content could be replaced with a single code block showing ER diagram syntax and would be infinitely more useful.
Suggestions
Add actual Mermaid ER diagram syntax with a complete, executable example (e.g., `erDiagram CUSTOMER ||--o{ ORDER : places`)
Include relationship notation reference (||--||, ||--o{, }o--o{, etc.) with brief explanations of cardinality
Provide 2-3 concrete examples showing common ER diagram patterns (one-to-many, many-to-many, self-referential)
Remove all generic boilerplate sections (Purpose, When to Use, Capabilities, Example Triggers) and replace with actionable content
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual value. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler that Claude already understands conceptually. | 1 / 3 |
Actionability | There is zero concrete guidance, no code examples, no Mermaid ER diagram syntax, and no executable instructions. The skill describes what it does abstractly but never shows how to actually create an ER diagram. | 1 / 3 |
Workflow Clarity | No workflow is provided whatsoever. There are no steps for creating ER diagrams, no validation checkpoints, and no process to follow. The 'step-by-step guidance' mentioned is never actually delivered. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic text with no structure pointing to detailed materials, no references to examples or syntax guides, and no organization beyond superficial headings. | 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
0c08951
- 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.