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
Quality
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 placeholder that provides almost no useful information for skill selection. It repeats the skill name as trigger terms, lacks any concrete capability descriptions, and provides no guidance on when to activate. The description would be nearly useless in a multi-skill environment where Claude needs to distinguish between similar tools.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates system architecture diagrams, cloud infrastructure visualizations, and component relationship maps using standard notation.'
Add a 'Use when...' clause with natural trigger terms: 'Use when the user asks to visualize system architecture, draw infrastructure diagrams, create AWS/Azure/GCP diagrams, or map component relationships.'
Include file format or output type information to improve distinctiveness, e.g., 'Outputs diagrams in SVG, PNG, or Mermaid syntax.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only states 'Architecture Diagram Creator' without listing any concrete actions. It doesn't specify what the skill actually does - no mention of creating, editing, exporting, or any specific diagram types or features. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and provides no 'when should Claude use it' guidance. There is no 'Use when...' clause or equivalent explicit trigger guidance. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundantly listed as 'architecture diagram creator, architecture diagram creator' (duplicated). Missing natural variations users would say like 'system diagram', 'infrastructure diagram', 'draw architecture', 'visualize system', 'AWS diagram', etc. | 1 / 3 |
Distinctiveness Conflict Risk | While 'architecture diagram' is somewhat specific compared to generic 'diagram' or 'visual', it could still overlap with other diagramming skills (flowcharts, UML, network diagrams). The category label 'Visual Content' is too broad to help differentiate. | 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 content is essentially a placeholder template with no actual instructional value. It describes what an architecture diagram creator skill should do without providing any concrete guidance, code examples, or workflows for actually creating diagrams. The content fails on all dimensions by being verbose yet empty of actionable information.
Suggestions
Add concrete Mermaid or PlantUML code examples showing how to create common architecture diagram types (C4, sequence, component diagrams)
Include a clear workflow: 1) Identify diagram type needed, 2) Draft structure, 3) Generate code, 4) Validate syntax, 5) Render and iterate
Remove all generic boilerplate ('provides automated assistance', 'follows best practices') and replace with specific diagram creation patterns
Add references to diagram syntax documentation and examples for different architecture diagram styles
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual value. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler that Claude doesn't need. | 1 / 3 |
Actionability | There is zero concrete guidance - no code, no commands, no specific examples of how to actually create architecture diagrams. The content only describes what the skill supposedly does without showing how to do anything. | 1 / 3 |
Workflow Clarity | No workflow is provided whatsoever. Despite claiming to provide 'step-by-step guidance,' there are no actual steps, no sequence, and no validation checkpoints for creating diagrams. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no references to detailed materials, no examples, and no links to actual diagram creation resources or syntax guides. | 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
0c08951
- 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.