mermaid-state-diagram-creator
Mermaid State Diagram Creator - Auto-activating skill for Visual Content. Triggers on: mermaid state diagram creator, mermaid state diagram creator Part of the Visual Content skill category.
35
3%
Does it follow best practices?
Impact
93%
0.97xAverage 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-state-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, consisting essentially of a repeated skill name and a category label with no substantive content. It fails to describe concrete capabilities, lacks natural trigger terms users would employ, and provides no guidance on when Claude should select this skill. It would be nearly indistinguishable from other Mermaid-related skills in a multi-skill environment.
Suggestions
Add concrete actions the skill performs, e.g., 'Creates Mermaid state diagrams with states, transitions, forks, joins, and nested states from textual descriptions.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks for state machine diagrams, state transition diagrams, FSM visualizations, or mentions stateDiagram syntax in Mermaid.'
Remove the duplicate trigger term and replace with varied natural language phrases users might say, such as 'state machine', 'state transitions', 'lifecycle diagram', 'FSM', or 'stateDiagram-v2'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the tool ('Mermaid State Diagram Creator') but does not describe any concrete actions like 'creates state diagrams', 'defines transitions', or 'generates stateDiagram-v2 syntax'. It is essentially just a title repeated with category metadata. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the title and completely lacks a 'when should Claude use it' clause. There is no explicit trigger guidance or use-case description. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('mermaid state diagram creator'). It lacks natural user phrases like 'state machine', 'state transitions', 'stateDiagram', 'flowchart of states', or 'FSM diagram' that users would actually say. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'state diagram' and 'mermaid' does narrow the domain somewhat, distinguishing it from generic diagram or flowchart skills. However, the lack of specificity about what it does versus other Mermaid diagram skills (flowcharts, sequence diagrams, etc.) still leaves some overlap risk. | 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 creating Mermaid state diagrams. It contains only meta-descriptions of what the skill would do without providing any Mermaid syntax, examples, or actionable guidance. It is entirely non-functional as a skill.
Suggestions
Add actual Mermaid state diagram syntax with executable examples, e.g., a complete `stateDiagram-v2` block showing states, transitions, and composite states.
Replace the meta-description sections ('When to Use', 'Capabilities', 'Example Triggers') with concrete instruction sections like 'Quick Start', 'Syntax Reference', and 'Common Patterns'.
Include at least 2-3 progressively complex examples (simple state machine, nested states, concurrent states) with rendered-ready Mermaid code blocks.
Add a validation step or checklist for common Mermaid state diagram errors (e.g., missing end states, invalid transition syntax).
| 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 instructions, code, or Mermaid syntax. Every section restates the same vague information. | 1 / 3 |
Actionability | There is zero concrete guidance—no Mermaid state diagram syntax, no code examples, no commands, no specific instructions. The content only describes rather than instructs. | 1 / 3 |
Workflow Clarity | No workflow or steps are provided. The mention of 'step-by-step guidance' is a claim with no actual steps defined anywhere in the content. | 1 / 3 |
Progressive Disclosure | The content has section headers but they contain no substantive information. There are no references to external files, no examples, and no structured navigation to deeper content. | 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.