Mermaid Sequence Diagram Creator - Auto-activating skill for Visual Content. Triggers on: mermaid sequence diagram creator, mermaid sequence diagram creator Part of the Visual Content skill category.
36
3%
Does it follow best practices?
Impact
100%
1.09xAverage 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-sequence-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, essentially consisting 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 visual or diagramming skills in a multi-skill environment.
Suggestions
Add concrete actions describing what the skill does, e.g., 'Creates Mermaid sequence diagrams from process descriptions, visualizes API call flows, and generates participant interaction timelines.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks for a sequence diagram, interaction diagram, Mermaid diagram, message flow visualization, or mentions sequenceDiagram syntax.'
Remove the duplicate trigger term and expand with varied natural phrases users might say, such as 'sequence diagram', 'mermaid syntax', 'interaction flow', 'message sequence chart', or 'API flow diagram'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the tool ('Mermaid Sequence Diagram Creator') but does not describe any concrete actions like 'generates sequence diagrams from text descriptions' or 'converts workflow steps into Mermaid syntax'. It is essentially just a title repeated. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' (no concrete actions described) and 'when should Claude use it' (no explicit 'Use when...' clause or equivalent guidance). It only states a category label. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('mermaid sequence diagram creator'). It lacks natural user phrases like 'sequence diagram', 'mermaid diagram', 'flow diagram', 'interaction diagram', or '.mmd' that users would actually say. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Mermaid Sequence Diagram' does narrow the domain somewhat, distinguishing it from general diagramming or other Mermaid diagram types. However, the lack of specificity about what it actually does and the vague 'Visual Content' category could cause overlap with other visual 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 content is an empty template/placeholder with no actual instructional value. It contains no Mermaid syntax, no sequence diagram examples, no concrete guidance of any kind—just repetitive meta-descriptions of what the skill would theoretically do. It fails on every dimension of the rubric.
Suggestions
Add actual Mermaid sequence diagram syntax with at least one complete, copy-paste-ready example (e.g., `sequenceDiagram` block with participants, messages, and activations).
Replace the meta-description sections ('Capabilities', 'Example Triggers', 'When to Use') with concrete guidance: common patterns (loops, alt blocks, notes), syntax rules, and pitfalls.
Include a quick-start section showing a minimal working sequence diagram and a more complex example demonstrating advanced features like opt/alt/loop fragments.
Add validation guidance—e.g., how to verify diagram renders correctly using Mermaid Live Editor or CLI tools.
| 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 syntax, examples, or useful information. Every section restates the same vague concept. | 1 / 3 |
Actionability | There is zero concrete guidance—no Mermaid sequence 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 phrase 'step-by-step guidance' is mentioned but never delivered. There are no sequences, validation checkpoints, or any procedural content. | 1 / 3 |
Progressive Disclosure | The content is a flat, monolithic block of boilerplate with no references to detailed materials, no links to examples or advanced guides, and no meaningful structural organization. | 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 | |
b8a3b3e
Table of Contents
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.