S³ Wireshark Analysis
v1.0.0This skill should be used when the user asks to "analyze network traffic with Wireshark", "capture packets for troubleshooting", "filter PCAP files", "follow...
⭐ 0· 142·0 current·0 all-time
bySolomon Neas@solomonneas
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Skill name/description match the SKILL.md content: guidance for capturing, filtering, reconstructing, and analyzing PCAPs with Wireshark. Declared prerequisites (Wireshark installed, interface and capture permissions, root for live captures) are reasonable and expected for this functionality.
Instruction Scope
SKILL.md contains step-by-step Wireshark capture and filter instructions and analytical workflows. It does not instruct the agent to read unrelated system files, access external endpoints, or exfiltrate data. It does note the need for administrator/root privileges for live capture, which is a legitimate operational requirement but has normal security implications.
Install Mechanism
No install spec or code is included (instruction-only). No downloads, package installs, or archive extraction are present.
Credentials
The skill does not request environment variables, credentials, or config paths. No disproportionate secret or credential access is required by the instructions.
Persistence & Privilege
Skill is not always-enabled and is user-invocable; model invocation remains allowed (the platform default). The skill does not request persistent system changes or modifications to other skills. The only privilege discussed is local administrator/root for live packet capturing, which is standard for capture tools.
Assessment
This skill is coherent and appears to be purely instructional for Wireshark usage. Before using it: (1) ensure Wireshark is installed from an official source (avoid third‑party builds), (2) be aware that packet captures often contain sensitive data (credentials, personal information); restrict captures and sanitize or redact PCAPs before sharing, (3) limit live captures with appropriate capture filters to avoid over‑collecting data, (4) avoid running Wireshark as root unless required for your platform—use the least privilege needed, and (5) do not upload captures to untrusted services. If you plan to allow any skill to act autonomously with access to captures, consider additional review because captured traffic can be sensitive.Like a lobster shell, security has layers — review code before you run it.
latestvk97ffg0g8nw51y3rq1kf5ydjc1837jpsnetworkvk97ffg0g8nw51y3rq1kf5ydjc1837jpspacket-capturevk97ffg0g8nw51y3rq1kf5ydjc1837jpspcapvk97ffg0g8nw51y3rq1kf5ydjc1837jpsprotocol-analysisvk97ffg0g8nw51y3rq1kf5ydjc1837jpswiresharkvk97ffg0g8nw51y3rq1kf5ydjc1837jps
License
MIT-0
Free to use, modify, and redistribute. No attribution required.