packet-analysis
/packet-analysis
Analyze network packet captures (.pcap/.pcapng) using Packet Buddy MCP. Use when opening a pcap file, inspecting packet captures, troubleshooting network traffic, analyzing retransmissions, or filtering packets by protocol.
- Author
- automateyournetwork ↗
- Repository
- netclaw ↗
- Licence
- Apache-2.0
- Last repository change
- 25.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 25.10.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
Analyze network packet captures (.pcap/.pcapng) using Packet Buddy MCP. Use when opening a pcap file, inspecting packet captures, troubleshooting network traffic, analyzing retransmissions, or filtering packets by protocol.
Original author description
Analyze network packet captures (.pcap/.pcapng) using Packet Buddy MCP. Use when opening a pcap file, inspecting packet captures, troubleshooting network traffic, analyzing retransmissions, or filtering packets by protocol.
How it works
- MCP Server
- Available Tools
- Workflow: Slack pcap Upload
- Workflow: Troubleshooting
- Common Display Filters
- Environment Variables
- Important Rules
- Failure Behavior
SKILL.md preview
--- name: packet-analysis description: "Analyze network packet captures (.pcap/.pcapng) using Packet Buddy MCP. Use when opening a pcap file, inspecting packet captures, troubleshooting network traffic, analyzing retransmissions, or filtering packets by protocol." version: 1.0.0 license: Apache-2.0 tags: [packets, pcap, wireshark, tshark, troubleshooting] --- # Packet Analysis Skill Installer note: native registration and the documented MCP_CALL invocation share the installed component launcher. Check `readiness.json` before first use; failed discovery is not device state. Existing write approvals still apply. ## MCP Server - **Script**: `$PACKET_BUDDY_MCP_SCRIPT` - **Invocation**: `python3 $MCP_CALL "python3 -u $PACKET_BUDDY_MCP_SCRIPT" <tool_name> '<json_args>'` ## Available Tools ### Discovery - **list_pcaps** — List all pcap files available for analysis - **pcap_summary** — High-level stats: packet count, duration, capture size ### Traffic Analysis - **pcap_protocol_hierarchy** — Protocol breakdown (what % is TCP, UDP, DNS, etc.) - **pcap_conversations** — Who talked to whom (IP, TCP, UDP, or Ethernet layer) - **pcap_endpoints** — Top talkers by traffic volume ### Filtering & Inspection - **pcap_filter** — Apply Wireshark display filters (e.g. `tcp.port==80`, `icmp`, `bgp`) - **pcap_packet_detail** — Full decode of a specific packet by number - **pcap_to_json** — Export packets as JSON for detailed analysis - **pcap_expert_info** — Warnings, errors, retransmissions, anomalies ### Protocol-Specific - **pcap_dns_queries** — Extract all DNS queries and responses - **pcap_http_requests** — Extract HTTP methods, URIs, and hosts ### File Management - **save_pcap_from_base64** — Save a base64-encoded pcap (e.g. from Slack file upload) ## Workflow: Slack pcap Upload When a user uploads a .pcap or .pcapng file in Slack: 1. The file arrives as a Slack file attachment 2. Download the file content and save it using **save_pcap_from_base64** 3. Run **pcap_summary** to give an overview 4. Ask the user what they want to investigate 5. Use appropriate tools to drill down ## Workflow: Troubleshooting When investigating a network issue with a pcap: 1. Start with **pcap_summary** for the big picture 2. Check **pcap_protocol_hierarchy** — any unexpected protocols? 3. Look at **pcap_conversations** — who's talking to whom? 4. Use **pcap_expert_info** for retransmissions, resets, errors 5. Apply **pcap_filter** to focus on specific traffic 6. Use **pcap_packet_detail** for deep inspection of suspect packets ## Common Display Filters | Filter | Purpose | |--------|---------| | `tcp.analysis.retransmission` | TCP retransmissions | | `tcp.flags.reset==1` | TCP RST packets | | `dns` | All DNS traffic | | `icmp` | Ping and ICMP errors | | `bgp` | BGP routing protocol | | `ospf` | OSPF routing protocol | | `tcp.port==22` | SSH traffic | | `http` | HTTP requests/responses | | `tls.handshake` | TLS handshakes | | `arp` | ARP requests/replies | | `stp` | Spanning Tree Protocol | | `ip.addr==10.0.0.1` | Traffic to/from specific host | ## Environment Variables - `PACKET_BUDDY_MCP_SCRIPT` — Path to packet-buddy-mcp/server.py - `PCAP_UPLOAD_DIR` — Directory for pcap files (default: /tmp/netclaw-pcaps) ## Important Rules - Large pcaps can be slow — use filters to narrow down - When showing results, summarize key findings rather than dumping raw output - Always check **pcap_expert_info** first — tshark already flags the problems - For Slack uploads, confirm the file was saved before attempting analysis ## Failure Behavior - If a tool call fails with an authentication or connection error, check that `PACKET_BUDDY_MCP_SCRIPT` is set and valid before assuming a data or device problem. - On a tool error (timeout, unreachable host, malformed response), report the failure and its error message directly to the user rather than fabricating or guessing at results. - For a confirmed read-only call, check connectivity and retry once if appropriate. For any call that changes state or sends a message, a timeout does not prove the action failed: inspect current state or delivery status before retrying, preserve the required approval/change gates, and do not repeat an action whose outcome is unknown.
Versions
The database has no other skills named packet-analysis.
Identical content appears in 1 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version 508852fcd999 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100pcap-analysis
Use when analyzing network packet capture files (.pcap, .pcapng) for DNS errors, TCP connection failures, HTTP proxy issues, or any network-level investigation using tshark on the local workstation - 100pcap-workflow
Performs safe offline packet-capture triage with TShark summaries, display filters, and clear-text HTTP metadata extraction. Use for PCAP/PCAPNG files, packet captures, Wireshark/TShark analysis, network forensics, 流量包, 抓包分析, 数据包分析, 网络取证, or 离线流量分析. - 100wireshark-traffic-analysis
Investigate pcap/pcapng captures through Wireshark MCP for traffic questions, network troubleshooting, and evidence-backed security analysis. Use when MCP tools are the selected backend; use tshark-cli-analysis for direct terminal execution. - 100wireshark-analysis
This skill should be used when the user asks to "analyze network traffic with Wireshark", "capture packets for troubleshooting", "filter PCAP files", "follow TCP/UDP streams", "detect network anomalies", "investigate suspicious traffic", or "perform protocol analysis". It… - 90protocol-traffic-analysis
Analyzes supplied PCAP and packet-capture evidence into hosts, conversations, dependencies, authentication exposure, timing patterns, blind spots, and defensible follow-up. Use when reviewing network traffic without transmitting to the observed systems. - 100netflows
Network flow extractor that analyzes pcap/pcapng files to identify outbound connections with automatic DNS hostname resolution. Use when you need to enumerate network destinations, identify what hosts a device communicates with, or map IP addresses to hostnames from packet captures.