mermaid-diagram

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

Quality

73%

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-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 highly actionable with a clear, validated workflow, but it is monolithic: heavy reference sections that should be split into separate files are inlined, and there is some redundancy from repeated emphasis and overlapping rule lists.

Suggestions

Move the CVPR/ICLR academic style guide, the KaTeX math reference, and the architecture junction techniques into separate files under references/ and link to them from the main workflow.

Consolidate 'Code Quality Rules' and 'Key Rules' into a single deduplicated list to remove overlapping restatements.

Reduce uppercase shouting ('MUST', 'MANDATORY', 'STRICT') and repeated imperative headers; trust Claude to follow concise directives.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with genuine non-obvious content (KaTeX math syntax, junction layout techniques), but carries repeated uppercase emphasis ('MUST', 'MANDATORY', 'STRICT') and redundant rule restatements across 'Code Quality Rules' and 'Key Rules' that could be trimmed.	3 / 5
Actionability	Provides copy-paste-ready bash commands (mkdir, mmdc/npx fallback), concrete file-output examples, executable Mermaid snippets, and a detailed KaTeX syntax table covering common cases.	5 / 5
Workflow Clarity	Steps 0-6 are explicitly sequenced with mandatory validation (mmdc render) and feedback loops (fix -> re-render -> re-verify up to MAX_ITERATIONS, plus a STRICT review FIX loop), satisfying the destructive/batch validation requirement.	5 / 5
Progressive Disclosure	Sections are well-organized with clear headers, but the ~410-line body inlines substantial reference material (academic style guide, KaTeX math reference, architecture junction techniques) that belongs in separate one-level-deep files, and no bundle references exist.	3 / 5
	Total	16 / 20 Passed

Description

70%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.

The description is specific and well-targeted to a distinct niche with good natural trigger terms, but it omits any explicit 'when to use' guidance, which limits its completeness.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when the user asks for diagrams, flowcharts, or visual representations of processes, architectures, or data models.'

Include the .mmd file extension and synonyms like 'diagram code' to broaden trigger-term coverage.

Consider mentioning the file-output and verification behavior to distinguish it from a pure code-generation skill.

Dimension	Reasoning	Score
Specificity	Names a concrete action ('Generate Mermaid diagrams from user requirements') and comprehensively enumerates supported types (flowcharts, sequence, class, ER, Gantt, +18 more), though it centers on a single action verb rather than listing several distinct actions.	4 / 5
Completeness	Clearly states what the skill does, but provides no 'Use when...' clause or equivalent trigger guidance, which per the rubric caps completeness at 3.	3 / 5
Trigger Term Quality	Includes natural terms users would say ('Mermaid diagrams', 'flowcharts', 'sequence diagrams', 'Gantt charts') with good coverage, but omits file extensions like .mmd and some synonyms.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche (Mermaid diagram generation) with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	16 / 20 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: 94d8093

Reviewed: 5 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.