BC Wireshark Network Traffic Analysis
Network traffic analysis with Wireshark and tshark. Capture packets, write display and BPF filters, follow TCP/UDP/TLS streams, detect C2 beacons, troubleshoot connectivity, and perform forensic PCAP analysis.
As a process C 59/100 · Has gaps — weak spots: result and completion, when it triggers, consistency
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 2
✓ No critical or high findings
Medium and low: 2
-
low Risky intent
intent-offensive-securityskill-card.md:2Offensive-security / dual-use content (legitimate for authorised testing; review intended use)Network traffic analysis with Wireshark and tshark for packet capture, filters, stream inspection, C2 beacon detection, connectivity troubleshooting, and forensic PCAP analysis. <br>
-
low Risky intent
intent-offensive-securitySKILL.md:444Offensive-security / dual-use content (legitimate for authorised testing; review intended use)**Scenario**: Identify command and control traffic
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 59/100
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 1 mutating operations with no state check
- 40Consistency. Frontmatter name (Wireshark Network Traffic Analysis) differs from the folder (wireshark-analysis)
- 50Failures and branches. 0 branches, has a failure section
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Tools and files. No external tools needed
- 100Steps. 52 steps
- 100Execution cost. Instruction body is 2924 tokens
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 209: enough signal without eating the budget
- +4Structure: 56 headings
- +3Step-by-step instructions: 52 items
- +4Has examples (25 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 67.
External checks
ClawHub: clean
This is an instruction-only Wireshark analysis guide whose sensitive packet-capture behavior is expected for its purpose and mostly disclosed.
LLM: benign (high) · VirusTotal: · 29 May 2026