Generate architecture documentation using C4 model Mermaid diagrams. Use when asked to create architecture diagrams, document system architecture, visualize software structure, create C4 diagrams, or generate context/container/component/deployment diagrams. Triggers include "architecture diagram", "C4 diagram", "system context", "container diagram", "component diagram", "deployment diagram", "document architecture", "visualize architecture".
90
86%
Does it follow best practices?
Impact
95%
1.69xAverage score across 3 eval scenarios
Passed
No known issues
Quality
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 clearly specifies what the skill does (C4 model Mermaid diagrams for architecture documentation), provides explicit 'Use when' guidance, and includes a comprehensive list of trigger terms that users would naturally say. The description is concise, uses third person voice, and carves out a distinct niche.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Generate architecture documentation', 'C4 model Mermaid diagrams', and explicitly names diagram types (context/container/component/deployment diagrams). | 3 / 3 |
Completeness | Clearly answers both what ('Generate architecture documentation using C4 model Mermaid diagrams') and when ('Use when asked to create architecture diagrams...') with an explicit list of triggers. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say, including 'architecture diagram', 'C4 diagram', 'system context', 'container diagram', 'component diagram', 'deployment diagram', 'document architecture', 'visualize architecture' - all terms users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Very clear niche focused on C4 model architecture diagrams specifically, with distinct triggers like 'C4 diagram', 'container diagram', 'component diagram' that are unlikely to conflict with general diagramming or documentation skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, actionable skill with excellent executable examples covering all C4 diagram types. The progressive disclosure is well-handled with clear references to supporting files. The main weakness is the workflow section lacks validation steps (e.g., verifying diagram renders, checking accuracy against codebase), and some syntax reference content could be trimmed since Claude knows Mermaid basics.
Suggestions
Add validation steps to the workflow, such as 'Verify diagram renders correctly in Mermaid preview' and 'Confirm with user that diagram accurately represents system'
Consider moving the detailed Element Syntax section to a reference file (references/c4-syntax.md) since it's already referenced, keeping only the most essential elements inline
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some redundancy - the element syntax section duplicates information Claude likely knows, and some explanatory text could be trimmed. However, it avoids explaining basic concepts like what C4 is or what Mermaid does. | 2 / 3 |
Actionability | Excellent executable examples throughout - every diagram type has complete, copy-paste ready Mermaid code. The syntax reference provides concrete element definitions, and the output location section gives specific file naming conventions. | 3 / 3 |
Workflow Clarity | The workflow section provides a clear 4-step sequence, but lacks validation checkpoints. There's no guidance on how to verify diagrams render correctly or validate that the architecture accurately represents the codebase before documenting. | 2 / 3 |
Progressive Disclosure | Well-structured with clear sections progressing from quick start to advanced patterns. References to external files (common-mistakes.md, c4-syntax.md, advanced-patterns.md) are clearly signaled and one level deep. The table-based level selection guide aids navigation. | 3 / 3 |
Total | 10 / 12 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
3027f20
Table of Contents
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.