network-diagram-generator
Network Diagram Generator - Auto-activating skill for Visual Content. Triggers on: network diagram generator, network diagram generator Part of the Visual Content skill category.
36
3%
Does it follow best practices?
Impact
100%
1.00xAverage 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/network-diagram-generator/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 extremely weak — it is essentially just the skill name repeated with boilerplate category metadata. It provides no concrete actions, no meaningful trigger terms, and no explicit guidance on when Claude should select this skill. It would be nearly useless for skill selection among a large set of available skills.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates network topology diagrams showing nodes, connections, subnets, routers, switches, and firewalls.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to create a network diagram, visualize network topology, map infrastructure, or draw network architecture.'
Include common file format or tool references users might mention, such as 'Mermaid diagrams', 'SVG output', 'infrastructure maps', or 'cloud architecture diagrams' to improve trigger term coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Network Diagram Generator') but does not describe any concrete actions like 'creates network topology diagrams', 'maps infrastructure connections', or 'generates node-link visualizations'. It is essentially just a label repeated. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and the 'when' clause is just a self-referential trigger ('network diagram generator'). There is no explicit 'Use when...' guidance with meaningful triggers. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'network diagram generator' repeated twice. It misses natural user phrases like 'network topology', 'infrastructure diagram', 'network map', 'nodes and connections', 'network architecture', or 'Visio-style diagram'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'network diagram' is somewhat specific to a niche (network topology visualization), which provides some distinctiveness. However, the vague 'Visual Content' category and lack of detail could cause overlap with other diagramming 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 placeholder that contains no actual instructional content. It repeatedly describes itself in abstract terms without providing any concrete guidance, code examples, tool usage, or workflows for generating network diagrams. It fails on every dimension of the rubric.
Suggestions
Add concrete, executable examples of network diagram generation using a specific tool (e.g., Mermaid syntax for network diagrams with a complete code block).
Define a clear workflow: e.g., 1) Gather network topology info, 2) Choose diagram type, 3) Generate Mermaid/D2/Graphviz code, 4) Validate rendering.
Remove all meta-description sections ('When to Use', 'Example Triggers', 'Capabilities') and replace with actual actionable content—input/output examples, supported diagram types, and syntax references.
Add references to related files or resources for advanced topics (e.g., 'See MERMAID_SYNTAX.md for full syntax reference') to support 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 concept. | 1 / 3 |
Actionability | There is zero actionable content—no code, no commands, no concrete examples, no diagram syntax, no tool references. The 'capabilities' section describes what it could do but never actually does it. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The skill claims to provide 'step-by-step guidance' but contains none. There are no validation checkpoints or sequences of any kind. | 1 / 3 |
Progressive Disclosure | The content is a flat, repetitive document with no references to external files, no structured navigation, and no layered information. It mentions 'Related Skills' but provides no links or paths. | 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
b8a3b3e
- 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.