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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill mermaid-state-diagram-creator35
Quality
3%
Does it follow best practices?
Impact
93%
0.97xAverage score across 3 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/18-visual-content/mermaid-state-diagram-creator/SKILL.mdDiscovery
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 with metadata rather than a functional skill description. It lacks any explanation of capabilities, concrete actions, or guidance on when to use it. The redundant trigger terms and absence of natural user language make it poorly suited for skill selection among multiple options.
Suggestions
Add concrete actions describing what the skill does, e.g., 'Creates Mermaid state diagrams showing transitions, states, and conditions from textual descriptions or requirements.'
Add a 'Use when...' clause with natural trigger terms like 'state machine', 'state transitions', 'workflow states', 'state chart', or 'visualize system states'.
Include common variations of how users might request this, such as 'diagram showing states', 'state flow visualization', or 'mermaid stateDiagram syntax'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the tool ('Mermaid State Diagram Creator') without describing any concrete actions. There are no verbs indicating what the skill actually does - no 'creates', 'generates', 'converts', or similar action words. | 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 redundant (same phrase repeated twice: 'mermaid state diagram creator') and overly specific. Missing natural variations users would say like 'state machine', 'state chart', 'flowchart', 'diagram states', or 'visualize states'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Mermaid State Diagram' is somewhat specific to a particular diagram type, but 'Visual Content skill category' is vague and could overlap with many other visualization skills. The lack of specific use cases increases conflict 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 essentially an empty placeholder with no actual content. It describes what a Mermaid state diagram skill should do without providing any actual guidance, syntax, examples, or executable code. The entire content could be replaced with a single Mermaid state diagram code example that would be infinitely more useful.
Suggestions
Add actual Mermaid state diagram syntax with executable examples (e.g., `stateDiagram-v2\n [*] --> State1\n State1 --> State2`)
Include concrete examples showing common state diagram patterns: simple states, composite states, transitions with labels, and fork/join
Remove all generic boilerplate ('provides automated assistance', 'follows industry best practices') and replace with actual actionable content
Add a quick reference section showing the key Mermaid state diagram syntax elements with copy-paste ready code blocks
| 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 state diagrams. No syntax examples, no code, no actual instructions—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 state diagrams. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of unhelpful boilerplate with no references to detailed materials, examples, or syntax documentation that would be essential for a diagramming skill. | 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 | |
- 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.