architecture-diagram-creator
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill architecture-diagram-creatorArchitecture Diagram Creator - Auto-activating skill for Visual Content. Triggers on: architecture diagram creator, architecture diagram creator Part of the Visual Content skill category.
Overall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%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 description of concrete capabilities, and provides no guidance on when Claude should select this skill. The description would be indistinguishable from any generic diagramming tool.
Suggestions
Add specific capabilities: 'Creates software architecture diagrams, system component visualizations, network topology diagrams, and cloud infrastructure layouts'
Add a 'Use when...' clause with natural trigger terms: 'Use when the user asks to visualize system architecture, draw component diagrams, create flowcharts, or diagram infrastructure'
Include file format or output details: 'Generates diagrams in SVG, PNG, or Mermaid syntax for technical documentation'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Architecture Diagram Creator') without describing any concrete actions. There are no specific capabilities listed like 'creates system diagrams', 'visualizes component relationships', or 'generates flowcharts'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and provides no explicit 'when to use' guidance. The 'Triggers on' section is just the skill name repeated, not meaningful trigger conditions. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('architecture diagram creator' listed twice) and lack natural variations users would say like 'system diagram', 'draw architecture', 'visualize infrastructure', 'component diagram', or 'flowchart'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'architecture diagram' is somewhat specific to a domain, the lack of detail about what types of architecture diagrams (software, network, cloud, etc.) could cause overlap with other diagramming or visualization skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill content is essentially a placeholder template with no substantive guidance. It describes what an architecture diagram creator skill should do without providing any actual instructions, code examples, or concrete steps for creating diagrams. The content fails on all dimensions by being verbose yet empty of actionable information.
Suggestions
Add concrete code examples showing how to create architecture diagrams using Mermaid, PlantUML, or similar tools (e.g., actual diagram syntax for common patterns like microservices, cloud architecture)
Include a clear workflow: 1) Identify components, 2) Define relationships, 3) Generate diagram code, 4) Validate rendering, 5) Iterate on layout
Provide specific examples of input (architecture description) and output (diagram code) to make the skill actionable
Remove all generic boilerplate ('provides automated assistance', 'follows best practices') and replace with actual diagram creation techniques and patterns
| 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 links to examples, and no structured navigation to actual implementation guidance. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 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.