mermaid-diagram

Generate Mermaid diagrams from user requirements. Supports flowcharts, sequence diagrams, class diagrams, ER diagrams, Gantt charts, and 18 more diagram types.

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/mermaid-diagram/SKILL.md

Quality

Content

77%Weight 40%Scale 1-3

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

The content is highly actionable with a clear, well-validated workflow and executable examples, but it is verbose in places and lacks the progressive-disclosure file structure the body itself implies.

Suggestions

Trim decorative scaffolding (ASCII banners in the review template, and the 'Key Rules' section that restates the workflow steps) to reduce token load.

Move the large Academic Style Guide and Math Patterns sections into reference files (e.g. references/academic-style.md, references/math.md) and link them from the body, matching the 'reading reference documentation' instruction.

Add the actual reference documentation files the body tells Claude to read, or remove that instruction if built-in Mermaid knowledge is intended to suffice.

Dimension	Reasoning	Score
Conciseness	The body is mostly actionable but padded: the STRICT review template uses decorative ASCII banners and an 11-item 'Key Rules' section that largely restates earlier steps, adding tokens that do not earn their place.	2 / 3
Actionability	It provides copy-paste-ready bash (mkdir, mmdc, npx fallback), complete Mermaid code examples, concrete KaTeX syntax patterns with a pattern table, and a specific kebab-case naming convention.	3 / 3
Workflow Clarity	Steps 0-6 are clearly sequenced with an explicit verification checkpoint (mmdc render), a fix->re-verify feedback loop bounded by MAX_ITERATIONS=3, and a detailed review checklist.	3 / 3
Progressive Disclosure	The skill is a ~415-line monolithic SKILL.md with no references/scripts/assets bundle, yet the body instructs reading 'reference documentation' that is not provided as actual files; the academic style guide and math patterns could be split into reference files.	2 / 3
	Total	10 / 12 Passed

Description

67%Weight 40%Scale 1-3

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

The description is specific and distinctive about Mermaid diagram generation, but it lacks an explicit 'Use when' trigger clause, which limits completeness and weakens trigger-term coverage for natural user phrasings.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when the user asks to create a diagram, flowchart, or sequence diagram from a description or requirements.'

Include more natural user phrasings as trigger terms (e.g. 'diagram', 'flow chart', 'visualize a process', 'architecture diagram').

Consider whether the count '18 more' adds clarity or is filler that could be replaced with the most common remaining types.

Dimension	Reasoning	Score
Specificity	It lists multiple concrete capabilities — "Generate Mermaid diagrams", then enumerates flowcharts, sequence diagrams, class diagrams, ER diagrams, Gantt charts, and 18 more — matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	It clearly states what the skill does but has no 'Use when...' or equivalent explicit trigger clause, which per the guidelines caps completeness at 2 even though the 'what' is strong.	2 / 3
Trigger Term Quality	It names diagram types users would mention (flowcharts, sequence, ER, Gantt) but misses common natural phrasings like 'diagram', 'flow chart', or 'visualize' that a user would actually say, fitting the 'some relevant keywords but missing common variations' anchor.	2 / 3
Distinctiveness Conflict Risk	The Mermaid-specific niche and enumerated diagram types make it clearly distinguishable from other skills and unlikely to trigger for the wrong skill.	3 / 3
	Total	10 / 12 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 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	14 / 16 Passed

Repository: wanshuiyin/Auto-claude-code-research-in-sleep
Path: skills/mermaid-diagram/SKILL.md
Commit: 3e49e63

Reviewed: 9 days ago

Table of Contents

Discovery Implementation Validation

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.