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 essentially a template placeholder with no substantive content. It repeats the skill name as its only trigger term, provides no concrete actions or capabilities, and lacks any 'Use when...' guidance. It would be nearly useless for Claude to differentiate this skill from others in a large skill library.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates network topology diagrams showing nodes, connections, subnets, and routing paths from configuration data or user descriptions.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to create network diagrams, topology maps, infrastructure visualizations, or wants to visualize network architecture, subnets, routers, switches, or firewall layouts.'
Remove the duplicate trigger term and expand with natural variations users would say, such as 'network topology', 'network map', 'infrastructure diagram', 'network architecture diagram', 'draw a network'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain ('network diagram') but describes no concrete actions. There are no specific capabilities listed like 'generates topology diagrams', 'maps network nodes and connections', or 'creates infrastructure visualizations'. It only states it is a 'Network Diagram Generator' with no elaboration on what it actually does. | 1 / 3 |
Completeness | The 'what' is extremely weak (just the name repeated) and the 'when' is missing entirely. There is no 'Use when...' clause or equivalent explicit trigger guidance. The description fails to answer either question meaningfully. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'network diagram generator' repeated twice, which is an exact duplicate rather than covering natural variations users might say (e.g., 'network topology', 'infrastructure diagram', 'network map', 'network architecture', 'draw network'). Very poor keyword coverage. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'network diagram' is somewhat specific and distinguishes it from generic diagram or document skills. However, it could overlap with other diagramming or visualization skills since it doesn't clearly define its niche beyond the name. | 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 a hollow template with no substantive content. It contains no actionable instructions, no code examples, no tool-specific guidance, and no workflow for generating network diagrams. It reads as auto-generated boilerplate that would provide zero value to Claude beyond what it already knows.
Suggestions
Add concrete, executable examples of network diagram generation using specific tools (e.g., Mermaid network diagram syntax, D2, or Graphviz DOT language) with copy-paste ready code blocks.
Define a clear workflow: e.g., 1) Identify network components, 2) Choose diagram type (topology, logical, physical), 3) Generate diagram code, 4) Validate output renders correctly.
Remove all boilerplate sections ('When to Use', 'Example Triggers', 'Capabilities') that describe the skill meta-information rather than teaching how to perform the task.
Include at least one complete input-to-output example showing a network description being converted into a rendered diagram format.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is almost entirely filler and boilerplate. It explains what the skill does in vague, repetitive terms without providing any actual technical content. Phrases like 'Provides step-by-step guidance' and 'Follows industry best practices' are empty padding. | 1 / 3 |
Actionability | There is zero concrete, executable guidance. No code examples, no commands, no specific tools (e.g., Mermaid syntax, D2, Graphviz), no diagram formats, no actual instructions for generating network diagrams. The entire content describes rather than instructs. | 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 | There is no meaningful content to organize, no references to supporting files, and no bundle files exist. The structure is just a series of empty boilerplate sections with no navigational value. | 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
3a2d27d
- 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.