aris-mermaid-diagram

Generate Mermaid diagrams from user requirements. Saves .mmd and .md files to figures/ directory with syntax verification. Supports flowcharts, sequence diagrams, class diagrams, ER diagrams, Gantt charts, and 18 more diagram types.

Quality

68%

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/aris-mermaid-diagram/SKILL.md

The canonical home for this skill is mermaid-diagram in wanshuiyin/Auto-claude-code-research-in-sleep

Quality

Content

70%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 skill body is highly actionable with a clear, well-validated workflow and strong feedback loops. It is somewhat verbose and monolithic, inlining reference material that would benefit from being split into separate files.

Suggestions

Move the Math Formulas (KaTeX) reference, CVPR/ICLR academic style guide, and Architecture junction techniques into separate reference files (e.g., references/math.md, references/academic-style.md) referenced from SKILL.md to improve progressive disclosure.

Trim or remove the diagram-type use-case column ('Processes, decisions, steps') since Claude already knows what each diagram type is for.

Replace generic style platitudes in the academic guide ('clean white background', 'sans-serif fonts') with only the non-obvious specifics, or move them to the reference file.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and dense, but the diagram-type use-case table and parts of the academic style guide re-explain concepts Claude already knows and could be tightened.	3 / 5
Actionability	Provides copy-paste bash commands (mkdir, mmdc), complete Mermaid examples, and a KaTeX syntax table; minor gaps are the templated <diagram-name> placeholders.	4 / 5
Workflow Clarity	Steps 0-6 are clearly sequenced with a mandatory mmdc verification step, an explicit fix-rerun-retry feedback loop (MAX_ITERATIONS=3), and a strict review checklist.	5 / 5
Progressive Disclosure	No bundle files exist; all reference material (math syntax, academic style guide, architecture junction techniques, full diagram-type table) is inlined in one ~400-line file with sections but no file-level split.	3 / 5
	Total	15 / 20 Passed

Description

66%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, listing concrete actions and natural diagram-type keywords. Its main weakness is the missing 'Use when...' trigger clause, which caps completeness and slightly limits trigger-term quality.

Suggestions

Add a 'Use when...' clause (e.g., 'Use when the user asks for a Mermaid diagram, flowchart, sequence diagram, or any visual diagram from text descriptions.') to satisfy the 'when' half of completeness.

Include synonyms and file extensions (e.g., '.mmd', 'Mermaid charts') to broaden natural trigger-term coverage.

Mention PNG rendering/output in the action list so the output capability is fully represented.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('Generate Mermaid diagrams', 'Saves .mmd and .md files to figures/ directory', 'syntax verification') with minor gaps (no mention of PNG rendering or visual review).	4 / 5
Completeness	Clearly states the 'what' but provides no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the rubric.	3 / 5
Trigger Term Quality	Includes natural terms users would say ('Mermaid diagrams', 'flowcharts', 'sequence diagrams', 'class diagrams', 'ER diagrams', 'Gantt charts') but lacks synonyms/file extensions and trigger context.	4 / 5
Distinctiveness Conflict Risk	'Generate Mermaid diagrams' is a clear niche with distinct triggers and low conflict risk, though the absence of explicit trigger guidance keeps it just below 5.	4 / 5
	Total	15 / 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: OpenLAIR/dr-claw
Path: skills/aris-mermaid-diagram/SKILL.md
Commit: d51b64e

Reviewed: 6 hours 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.