architecture-diagram-creator
Architecture Diagram Creator - Auto-activating skill for Visual Content. Triggers on: architecture diagram creator, architecture diagram creator Part of the Visual Content skill category.
36
3%
Does it follow best practices?
Impact
99%
1.19xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/18-visual-content/architecture-diagram-creator/SKILL.mdQuality
Discovery
7%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 description is essentially a template placeholder with no substantive content. It repeats the skill name as its own trigger term, provides no concrete actions or capabilities, and lacks any meaningful 'Use when...' guidance. It would be nearly useless for Claude to distinguish this skill from others in a large skill library.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates software architecture diagrams including component diagrams, sequence diagrams, and system overviews using Mermaid or PlantUML syntax.'
Add an explicit 'Use when...' clause with diverse trigger scenarios, e.g., 'Use when the user asks to visualize system architecture, draw component relationships, create infrastructure diagrams, or illustrate microservice layouts.'
Include natural keyword variations users would actually say, such as 'system diagram', 'cloud architecture', 'infrastructure layout', 'component diagram', 'service map', 'tech stack visualization'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain ('architecture diagram') but describes no concrete actions. There are no specific capabilities listed like 'generates diagrams from code', 'creates flowcharts', or 'exports to SVG'. It only states the skill name and category. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and the 'when' clause is just a repetition of the skill name as a trigger rather than meaningful guidance. There is no explicit 'Use when...' clause with real trigger scenarios. | 1 / 3 |
Trigger Term Quality | The only trigger term listed is 'architecture diagram creator' repeated twice. It misses natural variations users would say like 'system diagram', 'architecture overview', 'draw architecture', 'component diagram', 'infrastructure diagram', 'cloud architecture', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'architecture diagram' is somewhat specific and distinguishes it from general diagramming or document skills, but the lack of detail about what kind of architecture diagrams (software, cloud, network) and the vague 'Visual Content' category could cause overlap with other diagram or visualization skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty shell—a template placeholder that contains no actual instructional content. It describes what it would do in abstract terms but provides zero actionable guidance on creating architecture diagrams. There are no code examples (e.g., Mermaid syntax), no tool recommendations, no workflows, and no concrete instructions of any kind.
Suggestions
Add concrete, executable examples of architecture diagram creation using specific tools (e.g., Mermaid diagram syntax, PlantUML, or D2) with copy-paste ready code blocks.
Define a clear workflow: gather requirements → choose diagram type → write diagram code → render/validate → iterate, with specific validation steps.
Remove all meta-description sections ('When to Use', 'Example Triggers', 'Capabilities') that describe the skill abstractly and replace them with actual instructional content.
Include references to detailed guides for specific diagram types (e.g., SEQUENCE_DIAGRAMS.md, CLOUD_ARCHITECTURE.md) to provide progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual instructions, code, or concrete guidance. Every section restates the same vague information. | 1 / 3 |
Actionability | There is zero actionable content—no code, no commands, no concrete examples, no diagram syntax, no tool references. The 'capabilities' section lists abstract promises ('provides step-by-step guidance') without delivering any actual guidance. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, no validation checkpoints. The skill claims to provide 'step-by-step guidance' but contains none. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of meta-descriptions with no references to detailed files, no structured navigation, and no separation of overview from detailed content. There is nothing to progressively disclose because there is no substantive content. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
4dee593
- 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.