CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

mermaid-js

Use when selecting a Mermaid diagram type, looking up Mermaid syntax, adapting a Mermaid example, or locating a Mermaid reference for a flowchart, sequence, UML, architecture, chart, or other diagram.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

77%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-disciplined router: lean, unambiguous in its single routing action, with a clear need→file table and explicit escalation and ownership boundaries. Its one real defect is that the five referenced bundle files are absent from the provided skill directory, leaving the progressive-disclosure chain unverifiable, and the version/date notice sits outside a dedicated scope section.

Suggestions

Ship the five referenced files (QUICK_REFERENCE.md, DIAGRAM_INDEX.md, mermaid-diagram-reference.md, COOKBOOK.md, README.md) alongside SKILL.md — or move them under references/ and update the link paths — so the router's one-level-deep navigation actually resolves.

Fold the snapshot version and date (v11.12.3, 2026-03-07) into a dedicated 'Snapshot scope' subsection so the time-sensitive details are quarantined rather than woven into the routing guidance.

Tighten 'Related ownership' to a single line (e.g., 'For constructing or debugging Mermaid diagrams, use `process-siren:mermaids-treasure`; this skill only routes reference material.') and add one concrete example row mapping a sample request to a file to sharpen the routing decision.

DimensionReasoningScore

Conciseness

The body is lean — a short routing table plus brief boundary notes, with no concept-explaining padding and an explicit 'Do not copy reference material into this router' discipline. Not 5: the time-sensitive version/date details ('Mermaid v11.12.3, recorded on 2026-03-07') sit in the 'Reference status' section rather than an 'old patterns'/'deprecated'-style section, and the three-sentence 'Related ownership' paragraph runs longer than needed.

4 / 5

Actionability

The need→file routing table is concrete, executable guidance — for a router skill, 'Read QUICK_REFERENCE.md for declaration, common edges, styling' tells Claude exactly what to open, and 'Load only the reference needed' plus the escalation rule for current-version questions are directly actionable. Not 5: the 'Need' column entries are somewhat abstract categories ('choose a diagram type or compare diagram capabilities') and there is no concrete example of mapping a sample request to a row.

4 / 5

Workflow Clarity

This is a single-purpose router under 50 lines whose single action — match the request to a table row and read that one file — is unambiguous, with explicit precedence rules (snapshot vs. official docs for current-version questions; this skill vs. owning architecture/process skills). Per the simple-skill exception, a single unambiguous action scores 5. No destructive or batch operations exist, so no validation cap applies.

5 / 5

Progressive Disclosure

The in-file structure is the ideal router pattern — a clear overview, well-signaled one-level-deep links ('Declaration… → QUICK_REFERENCE.md', 'Full syntax… → mermaid-diagram-reference.md'), and a 'Load only the reference needed' instruction. However, scoring against the actual bundle structure: none of the five referenced files (QUICK_REFERENCE.md, DIAGRAM_INDEX.md, mermaid-diagram-reference.md, COOKBOOK.md, README.md) exist in the bundle as provided, so the one-level-deep navigation cannot resolve or be verified. Not 4: missing destination files are a structural break in the disclosure chain, not a minor organization gap; not 2: the references are clearly signaled and no detail content is wrongly inlined.

3 / 5

Total

16

/

20

Passed

Description

80%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description with explicit 'Use when' triggers, four concrete actions, and good natural keyword coverage anchored by the Mermaid name. The main weakness is that the underlying capability is only implied through gerunds inside the trigger clause rather than stated directly, and a few common synonyms (gantt, ER/class diagrams, .mmd) are absent.

DimensionReasoningScore

Specificity

The description lists four concrete, distinct actions — 'selecting a Mermaid diagram type', 'looking up Mermaid syntax', 'adapting a Mermaid example', 'locating a Mermaid reference' — with a comprehensive domain list ('flowchart, sequence, UML, architecture, chart, or other diagram'), matching the top anchor for multiple specific concrete actions with comprehensive coverage. Not 4: there is no minor gap in the action list; each action is named and concrete.

5 / 5

Completeness

The 'when' is explicit and strong — the description opens with 'Use when selecting… looking up… adapting… or locating…', satisfying the 'Use when...' requirement with concrete triggers. Not 5: the 'what' is never stated as a distinct capability; the actions appear only as gerunds fused into the trigger clause, and the underlying function (routing to a bundled Mermaid reference snapshot) is left implicit. Not 3: the gerunds do name concrete actions, so the 'what' is more than weakly implied.

4 / 5

Trigger Term Quality

Natural terms users would actually say are well covered: 'Mermaid', 'diagram type', 'flowchart', 'sequence', 'UML', 'chart', 'diagram', 'syntax'. Not 5: common synonyms and specific variations are missing (e.g., 'gantt', 'ER diagram', 'class diagram', 'state diagram', file extensions like '.mmd'), which the 5 anchor expects.

4 / 5

Distinctiveness Conflict Risk

'Mermaid' anchors the whole description to a clear niche with distinct triggers, and the enumerated diagram types are specific. Not 5: the trailing 'chart, or other diagram' is generic enough to overlap with general charting/visualization skills, a minor conflict risk with closely related skills. Not 3: the repeated Mermaid naming keeps it far more distinct than the 'somewhat specific' anchor.

4 / 5

Total

17

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 5 missing

Warning

Total

15

/

16

Passed

Repository

Jamie-BitFlight/claude_skills

Path

.claude/skills/mermaid-js/SKILL.md

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.