CtrlK
BlogDocsLog inGet started
Tessl Logo

mermaid-visualizer

Transform text content into professional Mermaid diagrams for presentations and documentation. Use when users ask to visualize concepts, create flowcharts, or make diagrams from text. Supports process flows, system architectures, comparisons, mindmaps, and more with built-in syntax error prevention.

64

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/mermaid-visualizer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 real Mermaid examples, concrete syntax fixes, and a sensible workflow backed by a quality checklist. Its main weakness is token redundancy from duplicating the reference's syntax rules in the body and from illustrative pseudocode sections.

Suggestions

Move the Critical Syntax Rules detail into references/syntax-rules.md and keep only a brief pointer plus the single most common pitfall in the body, reducing duplication with the reference file.

Replace the bracket pseudocode in Example Usage Patterns with a single concrete rendered example or remove the section, since the Common Patterns already show real Mermaid code.

Add an explicit fail→fix→regenerate feedback step in the Workflow so syntax errors caught by the Quality Checklist have a documented recovery path.

DimensionReasoningScore

Conciseness

The body avoids explaining concepts Claude already knows, but it duplicates the reference's syntax rules inline (Critical Syntax Rules mirrors references/syntax-rules.md's Critical Error Prevention) and includes illustrative-but-superfluous bracket pseudocode in Example Usage Patterns, so it is mostly efficient with clear room to tighten.

3 / 5

Actionability

It provides copy-paste-ready Mermaid code blocks (Swimlane, Feedback Loop, Hub and Spoke), concrete ✅/❌ syntax fixes, and explicit configuration options, but the Example Usage Patterns use bracket pseudocode rather than real generated output, leaving a minor gap.

4 / 5

Workflow Clarity

The numbered Workflow and Quick Start give a clear sequence and the Quality Checklist plus the "Test for common errors" step supply validation, but there is no explicit fail→fix→regenerate feedback loop, keeping it at 4 rather than 5.

4 / 5

Progressive Disclosure

Sections are well organized with clear headers and a single one-level-deep reference (references/syntax-rules.md, a real file), but the inlined Critical Syntax Rules duplicate the reference's content that could live solely in the reference file, a minor organization gap.

4 / 5

Total

15

/

20

Passed

Description

83%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 pairs a concrete capability statement with an explicit, natural-language trigger clause and names several specific diagram types. Its main weakness is slight generality in a few trigger phrases that could overlap with adjacent visualization skills.

DimensionReasoningScore

Specificity

"Transform text content into professional Mermaid diagrams" names the core action and "Supports process flows, system architectures, comparisons, mindmaps, and more" lists several concrete diagram types with only minor coverage gaps, fitting the 4-anchor more closely than the comprehensive 5-anchor.

4 / 5

Completeness

It explicitly states the "what" (transform text into Mermaid diagrams) and the "when" (Use when users ask to visualize concepts, create flowcharts, or make diagrams) with concrete trigger phrases, matching the 5-anchor.

5 / 5

Trigger Term Quality

"Use when users ask to visualize concepts, create flowcharts, or make diagrams from text" supplies good natural-keyword coverage (visualize, flowcharts, diagrams) but omits common synonyms like "charts" and has no file-extension-style triggers, so it sits at 4 rather than 5.

4 / 5

Distinctiveness Conflict Risk

"Mermaid diagrams" carves a clear niche with distinct triggers, but generic phrasing like "visualize concepts" and "make diagrams" leaves minor overlap risk with other visualization/charting skills, so it is 4 rather than 5.

4 / 5

Total

17

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
breferrari/obsidian-mind
Reviewed

Table of Contents

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.