automateyournetwork/netclaw/cml-packet-capture
Claude Code and agent skill by automateyournetwork/netclaw
- community
Checking that the SKILL.md file is still in the repository.
CML packet capture — start, stop, download pcaps from CML lab links, integrate with Packet Buddy for analysis. Use when capturing packets in a CML lab, troubleshooting BGP or OSPF with packet analysis, or downloading pcap files for Wireshark review.
Install
npx vskill@latest install automateyournetwork/netclaw/cml-packet-captureSKILL.md
The same SKILL.md was published earlier as automateyournetwork/netclaw/cml-packet-capture.
CML Packet Capture
MCP Server
- Command:
cml-mcp(pip-installed, stdio transport) - Requires:
CML_URL,CML_USERNAME,CML_PASSWORDenvironment variables
Available Tools
Packet Capture Operations
| Tool | Parameters | What It Does | |
|---|---|---|---|
start_capture | lab_id/lab_title, link_id, max_packets?, pcap_filter? | Start capturing packets on a link | |
stop_capture | lab_id/lab_title, link_id | Stop an active capture | |
get_capture_status | lab_id/lab_title, link_id | Check capture status (running, packet count) | |
download_capture | lab_id/lab_title, link_id, file_path? | Download the captured pcap file | |
list_captures | lab_id/lab_title | List all active and completed captures in a lab |
Workflow: Capture and Analyze (Full Pipeline)
When a user says "capture traffic between R1 and R2 and analyze it":
- Find the link: Use
get_links(from cml-topology-builder) to find the link ID between R1 and R2 - Start capture:
start_capturewith optional filter (e.g., "icmp", "tcp port 179") - Generate traffic: Tell the user to generate traffic (or use
execute_commandto ping) - Stop capture:
stop_captureafter sufficient traffic is collected - Download pcap:
download_captureto save the pcap file locally - Analyze with Packet Buddy: Hand off to the packet-analysis skill:
pcap_summary— overviewpcap_protocol_hierarchy— protocol breakdownpcap_conversations— who talked to whompcap_expert_info— errors, retransmissionspcap_filter— drill into specific traffic
- Report findings: Summarize the analysis in plain English
Workflow: Targeted Protocol Capture
When troubleshooting a specific protocol:
BGP Troubleshooting
OSPF Troubleshooting
ICMP / Connectivity
Spanning Tree
Capture Filters
CML uses BPF (Berkeley Packet Filter) syntax for capture filters:
| Filter | Captures | |
|---|---|---|
icmp | ICMP (ping) traffic | |
tcp port 179 | BGP traffic | |
ospf | OSPF traffic | |
tcp port 22 | SSH traffic | |
udp port 53 | DNS traffic | |
arp | ARP requests/replies | |
stp | Spanning Tree BPDUs | |
tcp port 80 or tcp port 443 | HTTP/HTTPS traffic | |
host 10.0.0.1 | Traffic to/from specific host | |
net 10.0.0.0/24 | Traffic to/from specific subnet | |
vlan 100 | Traffic on VLAN 100 |
Workflow: Compare Before/After
When verifying a configuration change:
- Capture before: Start capture, collect baseline traffic
- Stop and download: Save as
before.pcap - Make the change: Apply configuration via cml-node-operations
- Capture after: Start new capture, collect post-change traffic
- Stop and download: Save as
after.pcap - Compare: Analyze both pcaps with Packet Buddy
- Report: Document the differences (e.g., "BGP converged in 3s after route-map change")
Integration with Packet Buddy
After downloading a pcap from CML, use these Packet Buddy tools for analysis:
| Step | Packet Buddy Tool | Purpose | |
|---|---|---|---|
| 1 | pcap_summary | Big picture: packet count, duration, size | |
| 2 | pcap_protocol_hierarchy | What protocols are present | |
| 3 | pcap_conversations | Who is talking to whom | |
| 4 | pcap_expert_info | Errors, warnings, retransmissions | |
| 5 | pcap_filter | Focus on specific traffic | |
| 6 | pcap_packet_detail | Deep dive into a single packet | |
| 7 | pcap_dns_queries | DNS resolution analysis | |
| 8 | pcap_http_requests | HTTP traffic analysis |
Important Rules
- Lab must be running — captures only work on links in a started lab
- One capture per link — stop an existing capture before starting a new one
- Use filters for busy links — unfiltered captures on high-traffic links can be large
- Set max_packets — prevent runaway captures; 10000 packets is usually enough
- Download before stopping — some CML versions clear the capture buffer on link state change
- File naming: Save pcaps with descriptive names like
r1-r2-bgp-capture.pcap - Record in GAIT — log captures and findings for audit trail
Failure Behavior
- 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.
Security
- Security scanPassed, 82 of 100Pattern checks on the skill's files.
- Model reviewPassed
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingworkspace/skills/cml-packet-capture/SKILL.md
Popularity
- Repository stars
- 674
- Repository forks
- 189
- 7-day trend score
- 33
Stars and forks are for the whole GitHub repository, not this skill alone. Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/automateyournetwork/netclaw/cml-packet-capture)