mermaid-er-diagram-creator
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill mermaid-er-diagram-creatorMermaid 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.
Overall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is essentially a placeholder that provides minimal useful information for skill selection. It lacks concrete actions, natural trigger terms, and explicit usage guidance. The only distinguishing element is the specific mention of 'Mermaid ER Diagram' in the name, but this alone is insufficient for Claude to make informed skill selection decisions.
Suggestions
Add specific actions the skill performs, e.g., 'Creates entity-relationship diagrams using Mermaid syntax, visualizes database schemas, defines table relationships and cardinality'
Include a 'Use when...' clause with natural trigger terms like 'ER diagram', 'entity relationship', 'database schema', 'table relationships', 'data model visualization'
Remove the duplicate trigger term and expand to include variations users might naturally say, such as 'mermaid diagram', 'ERD', 'database diagram'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only states the skill name and category without describing any concrete actions. 'Mermaid Er Diagram Creator' names a tool but doesn't explain what it actually does (e.g., 'creates entity-relationship diagrams', 'defines database schemas visually'). | 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 trigger terms are just the skill name repeated twice ('mermaid er diagram creator'). Missing natural user phrases like 'ER diagram', 'entity relationship', 'database diagram', 'schema visualization', or 'mermaid diagram'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Mermaid Er Diagram' provides some specificity that distinguishes it from generic diagram tools, but 'Visual Content skill category' is vague and could overlap with many other visualization skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is entirely placeholder content with no actual instructional value. It describes what a skill should do rather than providing any concrete guidance on Mermaid ER diagram creation. The content lacks any Mermaid syntax examples, entity-relationship modeling patterns, or executable code.
Suggestions
Add concrete Mermaid ER diagram syntax examples showing entities, attributes, and relationships (e.g., `erDiagram CUSTOMER ||--o{ ORDER : places`)
Include a quick reference for relationship cardinality notation (||, |{, o{, etc.) and their meanings
Provide a complete, copy-paste ready example of a simple ER diagram with 2-3 entities
Remove all generic boilerplate text ('provides automated assistance', 'follows industry best practices') and replace with actual instructional 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 doesn't need. | 1 / 3 |
Actionability | There is zero concrete guidance on how to create Mermaid ER diagrams. No syntax examples, no code snippets, no actual Mermaid diagram markup - just vague descriptions of what the skill supposedly does. | 1 / 3 |
Workflow Clarity | No workflow is provided whatsoever. The skill claims to provide 'step-by-step guidance' but contains no actual steps for creating ER diagrams in Mermaid syntax. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic placeholder text with no structure pointing to useful resources, examples, or reference materials for Mermaid ER diagram syntax. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
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.