mermaid-sequence-diagram-creator
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill mermaid-sequence-diagram-creatorMermaid 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.
Overall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely underdeveloped, consisting primarily of auto-generated metadata rather than meaningful content. It fails to describe what the skill does, lacks natural trigger terms users would say, and provides no guidance on when Claude should select this skill. The duplicate trigger term suggests this may be a template that wasn't properly filled out.
Suggestions
Add specific capabilities: 'Creates Mermaid sequence diagrams showing participant interactions, message flows, loops, and conditional logic'
Include a 'Use when...' clause with natural triggers: 'Use when the user asks for sequence diagrams, interaction flows, API call visualizations, or mentions Mermaid syntax'
Add common user phrases as trigger terms: 'sequence diagram', 'interaction diagram', 'message flow', 'participant diagram', 'mermaid code', '.mmd files'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only states the skill name 'Mermaid Sequence Diagram Creator' without describing any concrete actions. It doesn't explain what the skill actually does (e.g., 'creates sequence diagrams', 'generates participant flows', 'visualizes interactions'). | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. There is no explanation of capabilities and no 'Use when...' clause or equivalent trigger guidance. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('mermaid sequence diagram creator, mermaid sequence diagram creator'). Missing natural user phrases like 'sequence diagram', 'flow diagram', 'interaction diagram', 'visualize process', or 'mermaid syntax'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Mermaid Sequence Diagram' provides some specificity that distinguishes it from generic diagram tools, but the lack of detail about specific use cases could cause overlap with other Mermaid or diagramming skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is entirely meta-content describing what a skill should do rather than providing any actual instruction on creating Mermaid sequence diagrams. It contains no Mermaid syntax, no diagram examples, no participant/message patterns, and no executable code. The content is essentially a placeholder template with no educational or practical value.
Suggestions
Add actual Mermaid sequence diagram syntax with executable examples (e.g., `sequenceDiagram\n Alice->>Bob: Hello`)
Include common sequence diagram patterns: participants, messages, loops, alt/opt blocks, notes
Provide 2-3 complete diagram examples showing different complexity levels (simple request-response, multi-participant flow, error handling)
Remove all meta-description content ('This skill provides...', 'When to Use...') and replace with actionable reference material
| 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 sequence diagrams. No syntax examples, no code snippets, no actual diagram patterns - 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, sequences, or processes for creating sequence diagrams. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of meta-description with no useful structure. There are no references to detailed materials, examples, or syntax guides that would be essential for a diagramming skill. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 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.