tessl install https://github.com/softaworks/agent-toolkit --skill mermaid-diagramsgithub.com/softaworks/agent-toolkit
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.
Average Score
92%
Content
85%
Description
100%
Generated
Validations
Total score
14/16| Criteria | Score |
|---|---|
skill_md_line_count SKILL.md line count is 217 (<= 500) | |
frontmatter_valid YAML frontmatter is valid | |
name_field 'name' field is valid: 'mermaid-diagrams' | |
description_field 'description' field is valid (731 chars) | |
description_voice 'description' uses third person voice | |
description_trigger_hint Description includes an explicit trigger hint | |
compatibility_field 'compatibility' field not present (optional) | |
allowed_tools_field 'allowed-tools' field not present (optional) | |
metadata_version 'metadata' field is not a dictionary | |
metadata_field 'metadata' field not present (optional) | |
license_field 'license' field is missing | |
frontmatter_unknown_keys No unknown frontmatter keys found | |
body_present SKILL.md body is present | |
body_examples Examples detected (code fence or 'Example' wording) | |
body_output_format Output/return/format terms detected | |
body_steps Step-by-step structure detected (ordered list) |
Content
Suggestions 2
Total score
11/12| Dimension | Score |
|---|---|
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 |
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
Overall Assessment
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.
Description
Total score
12/12| Dimension | Score |
|---|---|
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 |
Overall Assessment
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.