CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

conducting-internal-network-penetration-test

Execute an internal network penetration test simulating an insider threat or post-breach attacker to identify lateral movement paths, privilege escalation vectors, and sensitive data exposure within the corporate network.

Quality

74%

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 ./skills/conducting-internal-network-penetration-test/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%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, command-dense playbook with a clear five-phase structure and lean, competent writing. The main weaknesses are missing validation checkpoints for risky batch operations (capping workflow clarity) and a bundle whose reference files, scripts, and report template are never referenced from the body, leaving their content duplicated inline.

Suggestions

Add explicit validation checkpoints before risky or batch steps, e.g. verify cracked hashes with a single netexec login attempt before spraying, confirm account lockout policy before password spraying, and validate relay target SMB signing before running ntlmrelayx.

Link the existing bundle files instead of duplicating their content inline: point the Tools Reference to references/api-reference.md, Phase 5 to assets/template.md for the report template, and automation notes to scripts/process.py.

Trim the redundant "When to Use" bullets and the external-links References section (which duplicates references/standards.md) to reduce token cost.

DimensionReasoningScore

Conciseness

The body is dense, comment-annotated command blocks that assume Claude's competence with no padding explaining basic concepts, matching the "efficient; minor instances of over-explanation" anchor. Not 5 because the Tools Reference table and external-links References duplicate content shown in the commands (and in the bundle's reference files), and the "When to Use" bullets are partly redundant and awkwardly worded.

4 / 5

Actionability

Sixty-plus copy-paste-ready commands with realistic flags, targets, and placeholders cover the common cases of every phase — discovery, credential capture, cracking, lateral movement, privesc, domain escalation, and reporting. In-session snippets ("meterpreter> getsystem", "SQL> SELECT ...", smbclient "> dir") show exactly what to run rather than constituting gaps, so this matches the fully-executable anchor.

5 / 5

Workflow Clarity

Phases 1–5 provide a clear, logical sequence (discovery → credentials → exploitation/lateral → impact → reporting), but validation checkpoints are missing or only implicit for destructive and batch operations — password spraying across users.txt carries only a parenthetical lockout caution, and there is no verify-then-proceed step before relaying, lateral movement, or DCSync. Per the rubric's cap, a destructive/batch workflow without validation cannot score above 3.

3 / 5

Progressive Disclosure

Section structure is good (clear phase headers), but the actual bundle files are entirely orphaned — the body never links to references/api-reference.md, references/standards.md, references/workflows.md, assets/template.md, or scripts/agent.py and scripts/process.py — while their content (tools table, external reference links, report structure) is duplicated inline. This matches the anchor of references not clearly signaled and content that should be separate kept inline; not 2 because the body itself is well-organized and navigable rather than a monolithic wall.

3 / 5

Total

15

/

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 specific, domain-distinct description that names concrete capabilities (lateral movement, privilege escalation, data exposure) with natural trigger keywords. Its main weakness is the absence of any "Use when..." trigger guidance, which caps completeness, and limited synonym coverage for how users would phrase the request.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks for an internal network pentest, assumed-breach assessment, or wants to test lateral movement or privilege escalation inside a corporate network."

Include common natural variations users would say — "internal pentest", "Active Directory attack paths", "post-breach", "assumed breach" — to broaden trigger term coverage.

Mention additional concrete outcomes such as credential harvesting and attack-path reporting to round out capability coverage.

DimensionReasoningScore

Specificity

The description names the domain and lists several concrete capabilities — "identify lateral movement paths, privilege escalation vectors, and sensitive data exposure" — matching the anchor for several specific actions with minor gaps. It falls short of 5 because the primary verb ("Execute an internal network penetration test") restates the skill name and coverage areas like credential harvesting and reporting are absent.

4 / 5

Completeness

It clearly answers "what" (execute an internal pentest simulating an insider threat to identify lateral movement, privesc, and data exposure) but contains no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. Not 2 because the "what" is specific rather than vague.

3 / 5

Trigger Term Quality

Natural user phrasings are present ("internal network penetration test", "insider threat", "lateral movement", "privilege escalation", "sensitive data exposure"), giving good keyword coverage. Not 5 because common variations such as "pentest", "Active Directory", "post-exploitation", or "assumed breach" are missing.

4 / 5

Distinctiveness Conflict Risk

Terms like "internal network", "insider threat", "post-breach attacker", and "lateral movement" carve a distinct niche clearly separable from external/web application pentest skills. Only minor overlap risk with closely related AD-enumeration or red-team skills keeps it from a 5.

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

mukul975/Anthropic-Cybersecurity-Skills

Path

skills/conducting-internal-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.