network-security-scanner
Network Security Scanner - Auto-activating skill for Security Advanced. Triggers on: network security scanner, network security scanner Part of the Security Advanced skill category.
35
3%
Does it follow best practices?
Impact
92%
1.00xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/04-security-advanced/network-security-scanner/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 restates the skill name without providing any meaningful information about capabilities, concrete actions, or usage triggers. It lacks specificity, natural trigger terms, and completeness, making it nearly useless for Claude to distinguish this skill from others in a large skill library.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Scans network hosts for open ports, detects vulnerabilities, analyzes firewall configurations, and identifies security misconfigurations.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about port scanning, vulnerability scanning, network audits, nmap, open ports, or network penetration testing.'
Remove the redundant repeated trigger term and the boilerplate 'Auto-activating skill' / 'Part of the Security Advanced skill category' filler, replacing it with substantive capability descriptions.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain ('network security scanner') but provides no concrete actions. There is no mention of what the skill actually does—no verbs like 'scan', 'detect vulnerabilities', 'analyze ports', etc. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond restating the skill name, and the 'when' clause is just a redundant restatement of the title rather than explicit trigger guidance. There is no 'Use when...' clause. | 1 / 3 |
Trigger Term Quality | The only trigger term listed is 'network security scanner' repeated twice. It misses natural variations users would say like 'port scan', 'vulnerability scan', 'nmap', 'network audit', 'open ports', 'firewall check', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'network security scanner' is somewhat specific to a niche, but without concrete actions or distinct triggers, it could overlap with other security-related skills (e.g., vulnerability assessment, penetration testing, firewall configuration). | 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 template that provides zero actionable content about network security scanning. It contains no commands (e.g., nmap, masscan), no code examples, no scanning workflows, no safety constraints, and no actual guidance. It reads as auto-generated boilerplate that would add no value to Claude's context window.
Suggestions
Add concrete, executable examples of network security scanning tools and commands (e.g., nmap scan types, masscan usage, vulnerability scanner configurations) with specific flags and expected output formats.
Define a clear multi-step scanning workflow with validation checkpoints, such as: 1) scope verification, 2) discovery scan, 3) port scan, 4) vulnerability scan, 5) results validation and reporting.
Include explicit safety constraints and boundaries (e.g., only scan authorized targets, rate limiting, legal considerations, scope limitations) since this is a security-sensitive domain.
Remove all generic boilerplate sections ('When to Use', 'Example Triggers', 'Capabilities') and replace with actual technical content covering specific scanner tools, configuration patterns, and output interpretation.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler with no substantive information. It repeats 'network security scanner' excessively and explains nothing Claude doesn't already know. Every section is generic boilerplate with zero domain-specific content. | 1 / 3 |
Actionability | There are no concrete commands, code examples, tool invocations, or specific instructions. The skill describes what it could do ('provides step-by-step guidance') without actually providing any guidance whatsoever. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. There are no sequences, validation checkpoints, or any operational instructions for performing network security scanning tasks. | 1 / 3 |
Progressive Disclosure | The content is a flat, generic template with no references to detailed materials, no links to related files, and no structured navigation to deeper content. The sections are organizational theater with no real content to disclose. | 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
87f14eb
- 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.