draw-mermaid-diagrams

Draw and edit Mermaid diagrams in Markdown. Use when the user wants to visualize processes, flows, sequences, or asks for diagrams.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

82%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 content is well-structured and highly actionable, with executable examples and a clear validation script. Main gaps are a mild redundancy, an optional validation step lacking an explicit retry loop, and minor reference inconsistency.

Suggestions

Make validation a required checkpoint with an explicit feedback loop ("if errors, fix the syntax and re-run validation").

Use a single consistent path to SPEC.md and list the validation script in the Resources section for cleaner navigation.

Dimension	Reasoning	Score
Conciseness	The body is lean with no concept-padding and complete examples, but step 4 ("use the validation script to check for syntax errors") and the Validation section repeat the same purpose, a minor trimmable redundancy that keeps it just below 5.	4 / 5
Actionability	It provides a copy-paste-ready command ("deno run --allow-run --allow-read --allow-write --allow-env scripts/validate.ts path/to/diagram.mmd") plus complete, executable Mermaid examples covering common cases, matching the fully-executable anchor.	5 / 5
Workflow Clarity	A clear four-step sequence (identify type, consult spec, generate, validate) is present with validation as a named step, but validation is flagged optional and no explicit error-recovery/feedback loop is described, so it does not reach 5.	4 / 5
Progressive Disclosure	The body is an overview pointing one level deep to real files (SPEC.md for syntax, validate.ts via command) with well-organized sections; it is not 5 because SPEC.md is referenced two inconsistent ways ("SPEC.md" and "references/SPEC.md") and the Resources list omits the validation script.	4 / 5
	Total	17 / 20 Passed

Description

82%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 strong: it uses third person, names a distinct niche, and pairs a concrete capability statement with an explicit trigger clause. The only weakness is slightly limited action coverage and missing synonyms in the trigger set.

Suggestions

Expand the capability list beyond "Draw and edit" to concrete actions like "generate, edit, and validate" to lift specificity toward 4-5.

Add common synonyms such as "flowcharts", "charts", or ".mmd" files to the trigger clause for fuller natural-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ("Mermaid diagrams in Markdown") with two concrete actions ("Draw and edit"), matching the anchor that names a domain plus 1-2 concrete actions but is not comprehensive; it does not reach 4 because only two actions are listed with no broader coverage.	3 / 5
Completeness	It explicitly answers both what ("Draw and edit Mermaid diagrams in Markdown") and when ("Use when the user wants to visualize processes, flows, sequences, or asks for diagrams") with concrete trigger phrases, matching the top anchor exactly.	5 / 5
Trigger Term Quality	Natural trigger terms like "visualize processes, flows, sequences, or asks for diagrams" give good coverage a user would say; it stops short of 5 because synonyms (e.g., "charts", "flowcharts") and file-type cues are absent.	4 / 5
Distinctiveness Conflict Risk	"Mermaid diagrams in Markdown" is a clear, narrow niche with distinct diagram-oriented triggers and minimal overlap risk with other skills, matching the clear-niche anchor; it is not 4 because the niche is sharply bounded rather than merely "mostly distinct."	5 / 5
	Total	17 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: korchasa/flowai-plugins
Path: plugins/flowai-engineering/skills/draw-mermaid-diagrams/SKILL.md
Commit: b4ba256

Reviewed: ~20 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.