CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

conducting-network-penetration-test

Conducts comprehensive network penetration tests against authorized target environments by performing host discovery, port scanning, service enumeration, vulnerability identification, and controlled exploitation to assess the security posture of network infrastructure. The tester follows PTES methodology from reconnaissance through post-exploitation and reporting. Activates for requests involving network pentest, infrastructure security assessment, internal network testing, or external perimeter testing.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./skills/conducting-network-penetration-test/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 well-organized, highly actionable body whose workflow steps carry concrete, executable commands and genuine validation checkpoints. Its weaknesses are padded sections re-explaining concepts Claude already knows, an abstract exploitation step, and a progressive-disclosure failure: the bundled agent script and API reference are never referenced from the body at all.

Suggestions

Trim or remove the 'Key Concepts' table and 'Tools & Systems' descriptions — Claude already knows what CVSS, lateral movement, Nmap, and Metasploit are; keep only skill-specific guidance like the client-specific RoE requirements.

Reference the bundle files from the body, e.g., an 'Automation' section with 'python scripts/agent.py --target <cidr> --output report.json (see references/api-reference.md for CLI options and output schema)' — currently neither file is discoverable from SKILL.md.

Make the exploitation step concrete with an actual msfconsole example (e.g., 'use exploit/windows/http/tomcat_mgr_deploy; set RHOSTS <target>; run') instead of 'appropriate exploit modules matched to confirmed vulnerabilities'.

DimensionReasoningScore

Conciseness

The workflow steps are lean and command-dense, but the 'Key Concepts' table (defining CVSS, lateral movement, post-exploitation, Rules of Engagement) and the 'Tools & Systems' section (describing Nmap, Metasploit, Burp Suite) explain concepts Claude already knows. Mostly efficient with some unnecessary explanation that could be trimmed; not 2 because the majority of sections earn their tokens.

3 / 5

Actionability

Mostly executable: concrete copy-paste-ready commands with flags throughout (nmap -sS -p- --min-rate 1000, enum4linux -a, snmpwalk -v2c, dig axfr, impacket-psexec, linpeas/winPEAS) and a complete output template. Not 5 because the Metasploit bullet ('appropriate exploit modules matched to confirmed vulnerabilities. Set RHOSTS, RPORT...') and manual-exploitation guidance stay abstract without a single concrete msfconsole module example.

4 / 5

Workflow Clarity

A clear 7-step sequence with real validation checkpoints (WHOIS ownership verification in Step 1, lockout-policy respect in Step 5, cleanup verification by re-scanning in Step 7). Not 5 because there are no explicit error-recovery feedback loops (e.g., what to do when a scan triggers IDS or an exploit fails beyond 'document it'); not 3 because validation is present and explicit at the risky stages.

4 / 5

Progressive Disclosure

The body itself is well-structured with clear section headers, but the bundle contains references/api-reference.md and scripts/agent.py that are never mentioned anywhere in the body — the automation script and its API reference are undiscoverable from SKILL.md, and the ~30-line output format example plus the ~20-line scenario could live in reference files. References exist in the bundle but are not signaled at all, which blocks a 4; structure is good enough to stay above 2.

3 / 5

Total

14

/

20

Passed

Description

88%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 strong description that clearly defines a niche, enumerates concrete capabilities in third person, and includes an explicit activation clause with natural trigger terms. The only gaps are a few missing common synonyms (e.g., 'pen test', 'ethical hacking') and one slightly broad trigger phrase ('infrastructure security assessment').

DimensionReasoningScore

Specificity

The description lists five concrete actions ('host discovery, port scanning, service enumeration, vulnerability identification, and controlled exploitation') plus the PTES methodology span 'from reconnaissance through post-exploitation and reporting', giving comprehensive, concrete coverage of the skill's capabilities.

5 / 5

Completeness

Both 'what' and 'when' are explicitly answered: the 'what' enumerates the full capability set, and 'Activates for requests involving network pentest, infrastructure security assessment, internal network testing, or external perimeter testing' is an explicit trigger clause with concrete phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Trigger terms 'network pentest, infrastructure security assessment, internal network testing, or external perimeter testing' are phrases users would naturally say, but common synonyms like 'pen test' (spelled out), 'ethical hacking', 'red team', or 'vulnerability assessment' are missing. Not 5 because coverage lacks these natural variations; not 3 because the included terms are genuinely natural rather than jargon-only.

4 / 5

Distinctiveness Conflict Risk

The network penetration testing niche is clear and triggers are mostly distinct, but 'infrastructure security assessment' is broad enough to overlap with closely related skills (web application pentesting, cloud security assessment, vulnerability scanning). Not 5 due to this minor overlap risk; well above 3 because the core triggers (network pentest, internal/external network testing) are unambiguous.

4 / 5

Total

18

/

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

mukul975/Anthropic-Cybersecurity-Skills

Path

skills/conducting-network-penetration-test/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.