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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill network-diagram-generator36
Quality
3%
Does it follow best practices?
Impact
100%
1.00xAverage score across 3 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/18-visual-content/network-diagram-generator/SKILL.mdDiscovery
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 severely underdeveloped, essentially just restating the skill name without providing any meaningful information about capabilities or usage triggers. It reads like auto-generated boilerplate rather than a useful skill description. The redundant trigger terms and complete lack of action verbs or 'Use when' guidance make it nearly useless for skill selection.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates network topology diagrams, visualizes infrastructure layouts, generates connection maps between nodes and devices.'
Add an explicit 'Use when...' clause with natural trigger terms like 'network topology', 'infrastructure diagram', 'network map', 'visualize connections', 'server layout'.
Clarify the type of network diagrams supported (IT/infrastructure, cloud architecture, etc.) to distinguish from other diagramming skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only states 'Network Diagram Generator' without describing any concrete actions. It doesn't explain what the skill actually does - no mention of creating, editing, analyzing, or any specific capabilities. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and has no explicit 'Use when...' clause or equivalent guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('network diagram generator' listed twice) and overly narrow. Missing natural variations users might say like 'network topology', 'infrastructure diagram', 'network map', 'visualize network', etc. | 1 / 3 |
Distinctiveness Conflict Risk | While 'network diagram' is somewhat specific, the lack of detail about what kind of network diagrams (IT infrastructure, social networks, neural networks?) creates potential 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 essentially a placeholder template with no substantive content. It describes what a network diagram generator skill should do without providing any actual instructions, code examples, or concrete guidance. The entire content could be replaced with a single sentence and would convey the same (lack of) information.
Suggestions
Add executable code examples showing how to generate network diagrams (e.g., using Mermaid, D2, or Graphviz syntax)
Include specific input/output examples showing a network description and the resulting diagram code
Define a clear workflow: gather network components → choose diagram type → generate syntax → validate output
Remove all generic boilerplate ('provides automated assistance', 'follows best practices') and replace with concrete, actionable instructions
| 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 vague filler that Claude doesn't need. | 1 / 3 |
Actionability | There is zero concrete guidance - no code examples, no commands, no specific instructions on how to actually generate network diagrams. The content only describes what the skill supposedly does without showing how. | 1 / 3 |
Workflow Clarity | No workflow is defined. The skill claims to provide 'step-by-step guidance' but contains no actual steps, sequences, or processes for creating network diagrams. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic text with no references to detailed materials, no links to examples, and no structured navigation to additional resources. | 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 | |
- 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.