CtrlK
BlogDocsLog inGet started
Tessl Logo

mermaid-diagrams

Comprehensive guide for creating software diagrams using Mermaid syntax. Use when users need to create, visualize, or document software through diagrams including class diagrams (domain modeling, object-oriented design), sequence diagrams (application flows, API interactions, code execution), flowcharts (processes, algorithms, user journeys), entity relationship diagrams (database schemas), C4 architecture diagrams (system context, containers, components), state diagrams, git graphs, pie charts, gantt charts, or any other diagram type. Triggers include requests to "diagram", "visualize", "model", "map out", "show the flow", or when explaining system architecture, database design, code structure, or user/application flows.

Install with Tessl CLI

npx tessl i github:softaworks/agent-toolkit --skill mermaid-diagrams
What are skills?

Overall
score

92%

Does it follow best practices?

Validation for skill structure

SKILL.md
Review
Evals

Discovery

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is an excellent skill description that hits all the marks. It provides comprehensive specificity with numerous concrete diagram types and use cases, includes natural trigger terms users would actually say, explicitly addresses both 'what' and 'when' with clear trigger guidance, and carves out a distinct niche around Mermaid syntax diagramming that minimizes conflict risk with other skills.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions and diagram types: class diagrams, sequence diagrams, flowcharts, ERDs, C4 architecture diagrams, state diagrams, git graphs, pie charts, gantt charts, with specific use cases like 'domain modeling', 'API interactions', 'database schemas'.

3 / 3

Completeness

Clearly answers both what (creating software diagrams using Mermaid syntax with comprehensive list of diagram types) AND when (explicit 'Use when' clause with detailed triggers and a 'Triggers include' section listing specific user phrases).

3 / 3

Trigger Term Quality

Excellent coverage of natural trigger terms users would say: 'diagram', 'visualize', 'model', 'map out', 'show the flow', plus domain-specific terms like 'system architecture', 'database design', 'code structure', 'application flows'.

3 / 3

Distinctiveness Conflict Risk

Clear niche focused specifically on Mermaid syntax diagrams with distinct triggers around visualization and diagramming. The specificity of 'Mermaid syntax' and the comprehensive list of diagram types makes it unlikely to conflict with other skills.

3 / 3

Total

12

/

12

Passed

Implementation

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a well-structured skill with excellent actionability through concrete, executable Mermaid examples. The progressive disclosure is exemplary, providing quick-start content with clear pointers to detailed references. The main weakness is some verbosity in sections like 'Best Practices' and 'When to Create Diagrams' that explain concepts Claude already understands.

Suggestions

Remove or significantly condense the 'Best Practices' and 'When to Create Diagrams' sections - Claude already knows when diagrams are useful and general documentation practices

Tighten the 'Diagram Type Selection Guide' by removing the bullet point explanations under each type - the type name and one-line description are sufficient

DimensionReasoningScore

Conciseness

The content is generally efficient but includes some unnecessary sections like 'When to Create Diagrams' and 'Best Practices' that explain concepts Claude already knows. The diagram type selection guide could be more compact.

2 / 3

Actionability

Provides fully executable Mermaid code examples for each major diagram type. Examples are copy-paste ready and demonstrate real-world use cases like API flows, database schemas, and domain models.

3 / 3

Workflow Clarity

For a diagramming skill, the workflow is appropriately simple - select diagram type, write syntax, render. The content clearly sequences from type selection to syntax to rendering/export options. No destructive operations require validation checkpoints.

3 / 3

Progressive Disclosure

Excellent structure with quick start examples in the main file and clear one-level-deep references to detailed guides for each diagram type. Navigation is well-signaled with descriptive links to reference files.

3 / 3

Total

11

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata' field is not a dictionary

Warning

license_field

'license' field is missing

Warning

Total

14

/

16

Passed

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.