mermaid-sequence-diagram-creator
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 essentially a title repeated as a trigger term with a category label. It lacks any concrete actions, natural trigger terms, or explicit guidance on when Claude should select this skill. It would be nearly indistinguishable from other diagramming skills and provides no useful information for skill selection.
Suggestions
Add specific concrete actions such as 'Creates Mermaid sequence diagrams from textual descriptions of system interactions, API calls, or process flows'.
Add an explicit 'Use when...' clause with natural trigger terms like 'sequence diagram', 'mermaid diagram', 'visualize API flow', 'interaction diagram', 'message flow'.
Remove the duplicated trigger term and replace with varied natural language phrases users would actually say, such as 'diagram interactions', 'show message sequence', or 'mermaid syntax'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain ('Mermaid Sequence Diagram') but does not describe any concrete actions. There are no verbs like 'creates', 'generates', 'converts', or 'edits' — just a label and category. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' (no actions described) and 'when should Claude use it' (no 'Use when...' clause or equivalent explicit trigger guidance). It is essentially just a title and category label. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('mermaid sequence diagram creator'). There are no natural user phrases like 'sequence diagram', 'mermaid diagram', 'flowchart', 'visualize interactions', or file format mentions. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Mermaid Sequence Diagram' is somewhat specific and narrows the domain, but the lack of concrete actions or triggers means it could overlap with other diagramming or Mermaid-related 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 template/placeholder with no actual instructional content about Mermaid sequence diagrams. It contains zero actionable information—no syntax examples, no diagram patterns, no code, and no workflow. Every section is generic boilerplate that could apply to any skill topic by swapping the name.
Suggestions
Add concrete Mermaid sequence diagram syntax with executable examples (e.g., a complete ```mermaid sequenceDiagram block showing participants, messages, activations, loops, and alt blocks).
Provide a clear workflow: 1) identify participants, 2) define message flow, 3) add control structures (loops/alt/opt), 4) validate syntax, 5) render and verify output.
Include specific patterns and best practices for sequence diagrams such as naming conventions, when to use activation bars, how to handle async messages, and common pitfalls.
Remove all boilerplate sections (Purpose, When to Use, Example Triggers) that add no value and replace with actual instructional content about Mermaid sequence diagram creation.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats the skill name excessively, and contains zero substantive information about creating Mermaid sequence diagrams. | 1 / 3 |
Actionability | There is no concrete guidance whatsoever—no Mermaid syntax, no code examples, no commands, no diagram patterns. The content describes rather than instructs, offering only vague platitudes like 'provides step-by-step guidance' without actually providing any. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. There are no instructions for creating a sequence diagram, no validation steps, and no sequencing of any kind. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic placeholder text with no references to supporting files, no structured navigation, and no meaningful organization of content. There are no bundle files to reference either. | 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
3a2d27d
- 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.