Stats
Actions
Tags
From embedded-target
Capture and analyze traffic on a video-heavy embedded link — headers-only ring buffer always on, control-plane in full, batch tshark analysis the agent reads as conclusions. Use when diagnosing protocol, loss, reordering, jitter, or timing bugs on the device's network.
How this skill is triggered — by the user, by Claude, or both
Slash command
/embedded-target:network-captureThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Full pcap of a video stream is infeasible and unnecessary — protocol and timing bugs live in headers, sequence numbers, and timestamps; the payload is enormous by comparison and rarely needed.
Full pcap of a video stream is infeasible and unnecessary — protocol and timing bugs live in headers, sequence numbers, and timestamps; the payload is enormous by comparison and rarely needed.
tcpdump -s 128 -C <MB> -W <n> -w /var/log/pcap/ring. Snaplen ~96–128 bytes keeps Ethernet/IP/UDP/RTP headers and drops payload, cutting volume ~50–100×. RTP sequence numbers and timestamps survive — enough to detect loss, reordering, gaps, and jitter.tshark, not interactive Wireshark. Small scripts in harness/analyze/ (sequence-gap finder, inter-packet-time histogram, malformed-packet filter) so the agent reads conclusions, not packets. Wireshark stays the human tool for novel protocol forensics.collect-diag.sh snapshots the relevant ring window into the bundle.Templates: templates/harness/analyze/.
npx claudepluginhub destenson/agent-workflows --plugin embedded-targetGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.