Tessl • The package manager for agent skills

SkillPublic

mermaid-expert

Create Mermaid diagrams for flowcharts, sequences, ERDs, and architectures. Masters syntax for all diagram types and styling. Use PROACTIVELY for visual documentation, system diagrams, or process flows.

Quality

70%

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

Fix and improve this skill with Tessl

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

Quality

Content

50%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 well-structured and appropriately scoped for a simple single-purpose skill, but it relies heavily on generic boilerplate and high-level direction rather than concrete, executable Mermaid examples. Adding a minimal working diagram example would most improve actionability.

Suggestions

Replace the generic "Use this skill when / Do not use / Instructions" boilerplate with Mermaid-specific guidance, or remove it entirely to save tokens.

Add at least one copy-paste-ready Mermaid code example (e.g. a basic flowchart and a styled sequenceDiagram) under a Quick-start section to lift actionability.

Expand the Approach's "Test rendering before delivery" step into an explicit validate-then-fix feedback loop (render → if broken, fix syntax → re-render).

Dimension	Reasoning	Score
Conciseness	The Mermaid-specific sections are lean and assume Claude's competence, but the generic "Use this skill when / Do not use this skill when / Instructions" boilerplate (e.g. "Working on mermaid expert tasks or workflows", "Clarify goals, constraints, and required inputs") adds noticeable filler that earns its place poorly.	3 / 5
Actionability	Guidance stays high-level ("Choose the right diagram type", "Keep diagrams readable") with only a keyword list of diagram types; there are no executable, copy-paste Mermaid code examples showing actual syntax.	2 / 5
Workflow Clarity	The Approach section lists a 5-step sequence including "Test rendering before delivery" as a checkpoint, but the steps are high-level and lack explicit error-recovery feedback loops.	3 / 5
Progressive Disclosure	The body is under 50 lines, single-file, with no bundle files present, and is organized into clearly headed sections (Focus Areas, Diagram Types, Approach, Output), satisfying the simple-skill exception for progressive disclosure.	5 / 5
	Total	13 / 20 Passed

Description

78%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, well-triggered, and clearly distinct, answering both what the skill does and when to use it with concrete diagram-type keywords. Its main weakness is a mild over-claim ("Masters syntax for all diagram types") and trigger phrasing that could name a few more natural synonyms.

Dimension	Reasoning	Score
Specificity	Names the Mermaid domain and several concrete actions ("flowcharts, sequences, ERDs, and architectures", "styling"), with only minor coverage gaps; "Masters syntax for all diagram types" leans slightly toward over-claim but stays concrete.	4 / 5
Completeness	Clearly states what it does ("Create Mermaid diagrams for...") and gives an explicit when-clause ("Use PROACTIVELY for visual documentation, system diagrams, or process flows"), though the trigger phrasing could be marginally more specific.	4 / 5
Trigger Term Quality	Good coverage of natural terms users would say ("Mermaid diagrams", "flowcharts", "system diagrams", "process flows"), though a few common variants (e.g. "diagram", ".mmd") are missing.	4 / 5
Distinctiveness Conflict Risk	"Mermaid diagrams" is a clear, distinct niche with specific trigger phrases, giving minimal overlap risk with other skills.	5 / 5
	Total	17 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: rmyndharis/antigravity-skills
Path: skills/mermaid-expert/SKILL.md
Revision: 364ea63

Reviewed: 21 days ago

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.

mermaid-expert

Table of Contents

Is this your skill?