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 essentially a title and category label with no substantive content. It lacks concrete actions, natural trigger terms, and any 'Use when...' guidance. It would be nearly indistinguishable from other visual or diagramming skills in a large skill library.
Suggestions
Add specific actions the skill performs, e.g., 'Creates and edits Mermaid state diagrams (stateDiagram-v2) with states, transitions, forks, joins, and notes.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks for a state machine diagram, state chart, stateDiagram, or wants to visualize states and transitions in Mermaid syntax.'
Remove the duplicate trigger term and expand with natural variations users might say, such as 'state machine', 'state flow', 'FSM diagram', 'transition diagram'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain ('Mermaid State Diagram') but does not describe any concrete actions. There are no verbs like 'create', 'generate', 'edit', or 'convert' — just a label and category assignment. | 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. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('mermaid state diagram creator'). There are no natural user phrases like 'state machine', 'stateDiagram', 'flowchart states', 'transitions', or 'state chart'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Mermaid State Diagram' is somewhat specific and narrows the domain, but the lack of concrete actions or trigger terms means it could overlap with other Mermaid or diagramming skills without clear differentiation. | 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 shell—a boilerplate template with no actual content about Mermaid state diagrams. It contains no syntax examples, no diagram patterns, no executable code, and no actionable guidance whatsoever. It fails on every dimension because it describes what a skill would do rather than actually doing it.
Suggestions
Add concrete Mermaid state diagram syntax with at least one complete, copy-paste-ready example (e.g., `stateDiagram-v2` block with states, transitions, and notes).
Include specific patterns for common state diagram scenarios: simple states, composite/nested states, forks/joins, choice nodes, and history states.
Provide a quick-start section showing the minimal valid state diagram and then build up to advanced features with clear examples.
Remove all meta-description boilerplate ('This skill provides automated assistance...', 'Example Triggers', etc.) 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 state diagram syntax, examples, or useful information. Every token is wasted on boilerplate. | 1 / 3 |
Actionability | There is zero concrete guidance—no Mermaid syntax, no code examples, no commands, no state diagram patterns. The content only describes itself rather than instructing Claude how to create state diagrams. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, no sequences, and no validation checkpoints. The phrase 'step-by-step guidance' is promised but never delivered. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of meta-description with no meaningful structure, no references to detailed materials, and no actual content to organize or 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.