CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

conducting-man-in-the-middle-attack-simulation

Simulates man-in-the-middle attacks using Ettercap, mitmproxy, and Bettercap in authorized environments to intercept, analyze, and modify network traffic for testing encryption enforcement, certificate validation, and detection capabilities.

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/conducting-man-in-the-middle-attack-simulation/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 offensive-testing workflow with strong executable commands, explicit validation, and a useful scenario/pitfalls section. Its weaknesses are padded concept/tool explanations Claude already knows and a monolithic structure that ignores the skill's own bundle files.

Suggestions

Remove or drastically trim the 'Key Concepts' and 'Tools & Systems' sections — they re-explain concepts (HSTS, ARP poisoning, what Wireshark is) that Claude already knows.

Link the existing bundle files from the body (e.g., 'Full command reference: see references/api-reference.md; automation script: scripts/agent.py') and move per-tool detail there so the SKILL.md is a lean overview.

Convert comment-only validation steps in Steps 5 and 6 (Cisco DAI log check, target-side ARP cache refresh) into executable commands or a short verification checklist with a retry/recovery step.

DimensionReasoningScore

Conciseness

The bulk of the body is lean, executable command blocks, but the 'Key Concepts' table (MITM, SSL Stripping, HSTS, ARP Cache Poisoning) and 'Tools & Systems' section explain concepts and tools Claude already knows, which is unnecessary padding.

3 / 5

Actionability

Mostly copy-paste-ready guidance — complete bettercap/ettercap/mitmproxy command sequences, a fully written Python mitmproxy script, and concrete validation commands — with minor gaps where several Step 5/6 checks are comment-only placeholders (e.g., '# On Cisco switch: show ip arp inspection log').

4 / 5

Workflow Clarity

Six clearly sequenced steps with an explicit validation step (Step 5) and a cleanup/restore step (Step 6), so the destructive-operation cap does not apply; however, there is no explicit error-recovery feedback loop (e.g., what to do if the target loses connectivity mid-test) and some checkpoints are comments rather than commands.

4 / 5

Progressive Disclosure

Section headers are clear, but the body never references the existing bundle files (references/api-reference.md, scripts/agent.py), leaving them orphaned, and reference-worthy content (Key Concepts, Tools & Systems, per-tool detail) is inlined in the SKILL.md rather than split out.

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 specific, tool-named description with concrete actions and a clear niche, but it answers only 'what' and not 'when'. Adding an explicit 'Use when...' trigger clause with common synonyms (MITM, ARP spoofing, SSL stripping) would raise both completeness and trigger term quality.

Suggestions

Add an explicit trigger clause, e.g. 'Use when testing TLS/HTTPS enforcement, anti-MITM controls, or network detection capabilities, or when the user mentions MITM, ARP spoofing, or SSL stripping.'

Include common synonyms and abbreviations users would naturally say — 'MITM', 'ARP spoofing/poisoning', 'SSL stripping', 'traffic interception' — to improve trigger term coverage.

Mention the credential-capture/reporting outcomes of the simulation to close the small specificity gap.

DimensionReasoningScore

Specificity

The description lists several concrete actions ('intercept, analyze, and modify network traffic') with named tools (Ettercap, mitmproxy, Bettercap) and specific test purposes ('testing encryption enforcement, certificate validation, and detection capabilities'), leaving only minor coverage gaps (e.g., credential capture, reporting).

4 / 5

Completeness

The 'what' is clearly and specifically stated, but there is no 'Use when...' clause or equivalent trigger guidance — 'in authorized environments' is a scope qualifier, not a usage trigger, so completeness is capped at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

It includes natural phrases users would say ('man-in-the-middle attacks', 'network traffic', 'certificate validation', 'encryption'), but misses common variations such as 'MITM', 'ARP spoofing', 'SSL stripping', and 'traffic interception'.

4 / 5

Distinctiveness Conflict Risk

The MITM-simulation niche with named offensive tools is mostly distinct with minimal conflict risk, though it could overlap with adjacent network-security/pentest skills since no explicit trigger phrases distinguish it.

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-man-in-the-middle-attack-simulation/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.