Name: network-101
Rating: 49.6 (1 reviews)
Author: administrakt0r

network-101

Configure and test common network services (HTTP, HTTPS, SNMP, SMB) for penetration testing lab environments. Enable hands-on practice with service enumeration, log analysis, and security testing against properly configured target systems.

Quality

53%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/network-101/SKILL.md

The canonical home for this skill is network-101 in administrakt0r/AI-Agents-Safe-Coding-Skills

Quality

Content

46%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill provides broad coverage of four network services with mostly executable Linux commands, but suffers from significant verbosity, redundancy between sections, and a monolithic structure that would benefit from splitting into per-service files. Validation and error-recovery steps are relegated to a troubleshooting table rather than integrated into the workflow, and several sections contain information Claude already knows (port numbers, tool descriptions, what PDF-equivalent concepts like 'what SNMP is').

Suggestions

Split each service (HTTP, HTTPS, SNMP, SMB) into its own referenced file and keep SKILL.md as a concise overview with links, reducing the monolithic structure.

Remove redundant content: the Examples section largely duplicates the Core Workflow steps — either consolidate or differentiate them with distinct scenarios.

Add inline validation checkpoints after each configuration step (e.g., 'Verify service is listening: `ss -tlnp | grep :80` — if not shown, check `journalctl -u apache2`') rather than deferring all troubleshooting to a separate table.

Remove tables and explanations of things Claude already knows (port numbers, tool purposes, basic networking concepts) to improve token efficiency.

Dimension	Reasoning	Score
Conciseness	The skill is noticeably verbose with significant redundancy. HTTP setup appears in both the core workflow and examples sections with overlapping content. The Purpose section repeats the description. The ports table, enumeration tools table, and constraints section contain information Claude already knows. The 'When to Use' section is a meaningless placeholder.	2 / 5
Actionability	Most commands are concrete and executable with copy-paste ready bash commands for Linux setups. However, Windows instructions remain at the GUI-click level without PowerShell equivalents for most steps, and some commands use placeholder IPs without noting they need substitution. The SNMP config shows commented lines rather than actual file content to write.	4 / 5
Workflow Clarity	Steps are listed in a logical sequence for each service, and verification commands are provided. However, there are no explicit validation checkpoints or feedback loops — no 'if this fails, do X' patterns except in the troubleshooting table. For a skill involving service configuration (which can fail silently), missing inline validation steps between configure and use is a notable gap.	3 / 5
Progressive Disclosure	The content is a monolithic wall covering four distinct services in extensive detail, all inlined in a single file with no references to supporting files. Each service (HTTP, HTTPS, SNMP, SMB) could reasonably be its own file. There are no bundle files to reference, but the content length and breadth strongly calls for splitting into separate guides per service.	2 / 5
	Total	11 / 20 Passed

Description

61%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description identifies a clear domain (pen testing lab network services) and lists specific protocols, giving it reasonable specificity and distinctiveness. However, it lacks an explicit 'Use when...' clause, which is critical for Claude's skill selection, and the action verbs ('configure and test', 'enable hands-on practice') are somewhat generic rather than describing concrete operations.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks to set up a penetration testing lab, configure target services, or practice network enumeration techniques.'

Include additional trigger synonyms like 'pentest', 'Nmap', 'vulnerability scanning', 'network recon', or 'ethical hacking lab' to improve matching.

Make actions more concrete — instead of 'configure and test', specify operations like 'set up Apache/Nginx web servers, configure SNMP communities, deploy SMB shares with intentional misconfigurations'.

Dimension	Reasoning	Score
Specificity	Names the domain (network services for pen testing labs) and lists specific protocols (HTTP, HTTPS, SNMP, SMB), but the actions are somewhat generic — 'configure and test' and 'enable hands-on practice' lack concrete detail about what specific configuration or testing steps are performed.	3 / 5
Completeness	The 'what' is reasonably clear (configure/test network services for pen testing labs), but there is no explicit 'when' clause — no 'Use when...' guidance telling Claude when to select this skill. Per rubric guidelines, missing 'Use when' caps completeness at 3.	3 / 5
Trigger Term Quality	Includes good natural keywords like 'penetration testing', 'HTTP', 'HTTPS', 'SNMP', 'SMB', 'service enumeration', 'log analysis', 'security testing', and 'lab environments'. Missing some synonyms like 'pentest', 'network scanning', 'Nmap', 'vulnerability assessment', or 'infra testing'.	4 / 5
Distinctiveness Conflict Risk	The combination of specific protocols (HTTP, HTTPS, SNMP, SMB) with 'penetration testing lab environments' creates a fairly distinct niche. There's minor overlap risk with general network configuration or security testing skills, but the lab environment focus helps differentiate it.	4 / 5
	Total	14 / 20 Passed

Validation

90%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills/skills/network-101/SKILL.md
Commit: 57c135b

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.