CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

63%Weight 40%Scale 1-5

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

A highly actionable, well-sequenced skill body built almost entirely from real commands, weakened by duplication (Purpose, Examples, Quick Reference restate the workflow) and the absence of any reference files to offload the enumeration tool catalogs. Trimming duplicated sections and adding inline verification to the SNMP/SMB steps would raise both conciseness and workflow clarity.

Suggestions

Remove or merge the duplicated content: the Purpose section (verbatim description repeat), Examples 1-3 (restate Core Workflow commands), and the Quick Reference verification block could be consolidated or dropped, and the empty 'When to Use' section deleted entirely.

Split the per-service setup guides and the enumeration command catalogs into references/ files (e.g. references/snmp.md, references/smb.md) with one-level-deep, clearly signaled links from SKILL.md.

Add inline verification checkpoints to the SNMP and SMB steps (e.g. snmpwalk test after restart, smbclient -L check after smbd restart) and complete Example 3 by including the actual smb.conf share definition.

DimensionReasoningScore

Conciseness

The body is mostly executable commands rather than conceptual padding, but the Purpose section repeats the description verbatim, Examples 1-3 re-run Core Workflow steps, the Quick Reference duplicates enumeration commands, and the 'When to Use' section is filler that adds no information.

3 / 5

Actionability

Concrete, mostly copy-paste-ready bash blocks for every service plus specific Windows steps, but Example 3 never defines the smb.conf share it claims to configure, and the HTTPS step reduces to 'sudo nano /etc/apache2/sites-available/default-ssl.conf' without the actual configuration.

4 / 5

Workflow Clarity

Five clearly sequenced steps with explicit verification for HTTP ('curl http://localhost') and HTTPS ('nmap -p 443', 'openssl s_client'), plus a Troubleshooting table for error recovery, but SNMP and SMB steps lack inline verification checkpoints.

4 / 5

Progressive Disclosure

A single ~330-line file with no bundle files or external references; the per-service guides, enumeration command catalogs, and examples are all inlined where they could be split into well-signaled reference files.

3 / 5

Total

14

/

20

Passed

Description

66%Weight 40%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.

A solidly specific description that names concrete services and actions in third person, but it never tells Claude when to invoke it. Adding an explicit trigger clause (e.g., "Use when setting up pentest lab targets, configuring SNMP/SMB services, or practicing service enumeration") would move it into the top tier.

Suggestions

Append a 'Use when...' clause with concrete trigger phrases, e.g. 'Use when building a pentest lab, configuring target services (web, SNMP, SMB), or practicing service enumeration against lab targets.'

Add natural trigger synonyms such as 'web server', 'file share', 'Samba', 'Apache', and 'pentest lab' so the description matches how users actually phrase these requests.

State the deliverable context explicitly (e.g. 'for enumerating with nmap, snmpwalk, enum4linux') to sharpen distinctiveness against general sysadmin setup skills.

DimensionReasoningScore

Specificity

"Configure and test common network services (HTTP, HTTPS, SNMP, SMB)" plus "service enumeration, log analysis, and security testing" lists several concrete actions with named protocols, but coverage stops short of comprehensive per-service detail.

4 / 5

Completeness

The "what" is clear (configure and test HTTP/HTTPS/SNMP/SMB services for pentest labs), but there is no "Use when..." clause or equivalent explicit trigger guidance; the usage context is only weakly implied by "for penetration testing lab environments", which caps this at 3.

3 / 5

Trigger Term Quality

HTTP, HTTPS, SNMP, SMB, penetration testing, enumeration, and log analysis are natural terms users would say, but common synonyms like web server, Samba, file share, or lab setup are absent.

4 / 5

Distinctiveness Conflict Risk

The SNMP/SMB enumeration plus lab-environment framing carves a clear niche, though it could still overlap with generic web-server setup or general pentest-tooling skills.

4 / 5

Total

15

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

plugins/AI-Agents-Safe-Coding-Skills-claude/skills/network-101/SKILL.md

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.