CtrlK
BlogDocsLog inGet started
Tessl Logo

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

1.00x
Quality

3%

Does it follow best practices?

Impact

92%

1.00x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./planned-skills/generated/04-security-advanced/network-security-scanner/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

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 across all dimensions. It merely restates the skill name, provides no concrete actions or capabilities, duplicates its only trigger term, and lacks any explicit 'Use when...' guidance. It would be nearly indistinguishable from other security skills and provides no useful information for skill selection.

Suggestions

Add specific concrete actions the skill performs, e.g., 'Scans network hosts for open ports, detects vulnerabilities, identifies misconfigurations, and generates security reports.'

Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about port scanning, vulnerability assessment, network auditing, nmap, open ports, or firewall testing.'

Remove the redundant duplicate trigger term and replace boilerplate metadata ('Auto-activating skill for Security Advanced') with actionable capability descriptions.

DimensionReasoningScore

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 'scans ports', 'detects vulnerabilities', 'analyzes traffic', etc.

1 / 3

Completeness

The description fails to answer 'what does this do' beyond restating the skill name, and the 'when' clause is limited to a redundant trigger phrase with no explicit 'Use when...' guidance.

1 / 3

Trigger Term Quality

The only trigger terms listed are 'network security scanner' repeated twice. There are no natural variations a user might say such as 'port scan', 'vulnerability scan', 'nmap', 'network audit', 'open ports', etc.

1 / 3

Distinctiveness Conflict Risk

The term 'network security scanner' is somewhat specific to a niche, but the lack of concrete actions or distinct trigger terms means it could overlap with other security-related skills in a large skill set.

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 shell with no substantive content whatsoever. It consists entirely of meta-descriptions about what the skill supposedly does without providing any actual instructions, code, commands, tool usage, or technical guidance related to network security scanning. It fails on every dimension of the rubric.

Suggestions

Add concrete, executable examples of network security scanning commands (e.g., nmap scans with specific flags, vulnerability scanner configurations, output parsing scripts).

Define a clear multi-step workflow for conducting a network security scan, including reconnaissance, scanning, validation of results, and reporting, with explicit validation checkpoints.

Remove all meta-description sections ('When to Use', 'Capabilities', 'Example Triggers') and replace them with actionable technical content such as tool-specific configurations, common scan profiles, and result interpretation guidance.

Add references to supplementary files for advanced topics like compliance-specific scanning (SOC2, GDPR), threat modeling integration, or penetration testing methodologies.

DimensionReasoningScore

Conciseness

The content is entirely filler with no substantive information. It repeats 'network security scanner' numerous times without providing any actual technical guidance, commands, or configurations. Every section describes what the skill does rather than teaching how to do anything.

1 / 3

Actionability

There is zero actionable content—no code, no commands, no tool references, no concrete steps. Phrases like 'Provides step-by-step guidance' and 'Generates production-ready code' are meta-descriptions that don't actually deliver any guidance or code.

1 / 3

Workflow Clarity

No workflow is defined at all. There are no steps, no sequences, no validation checkpoints. The skill merely claims it provides 'step-by-step guidance' without actually containing any steps.

1 / 3

Progressive Disclosure

The content is a flat, repetitive structure with no references to detailed materials, no links to related files, and no meaningful organization of information across sections. The sections that exist are boilerplate 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.

Validation9 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

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

Repository
jeremylongshore/claude-code-plugins-plus-skills
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.