dngames

Wirebuddy — AI skill for Claude Code

AI community

A Wireshark-style packet viewer you and your AI agent use together, over MCP.

How to install Wirebuddy

This entry records only its repository, not the path inside it, so there is no exact command to give. Open dngames/wirebuddy and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Wirebuddy does

A Wireshark-style packet viewer you and your AI agent use together, over MCP.

Alternatives in AI

Anthropic Quickstarts — by Anthropic - Offers comprehensive development guides for three distinct AI-powered demo projects with standa 15.4k ★
Style Distill — style-distill skill — 三阶段 13 模板 LLM 蒸馏（style-distill-order） 669 ★
Karpathy LLM Wiki — Agent Skills-compatible LLM wiki for Claude Code, Cursor, and Codex 618 ★

README

WireBuddy

[![CI](https://github.com/dngames/wirebuddy/actions/workflows/ci.yml/badge.svg)](https://github.com/dngames/wirebuddy/actions/workflows/ci.yml) [![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](LICENSE)

50-second demo · MP4 version

**You and your AI agent, looking at the same packets.**

WireBuddy is a Wireshark-style packet viewer in a browser tab, built to sit next to an AI chat (for example in the Claude Code desktop app's browser pane). The agent works the viewer over MCP while you watch and click in the same view, and when a capture holds something Wireshark can't decode or a packet list can't show, the agent extends the viewer itself.

One view for both of you. The agent's filters, selected packet, marks, comments and columns show up in your view as it works, each with a notice; what you do there (open a file, apply a filter, start a capture) reaches the agent with its next call, and it sees which packets you selected. Right-click packets to ask the agent about them without leaving the view. You check its findings in the packets instead of taking a summary on trust.
The agent extends the viewer. Traffic Wireshark doesn't know, such as a company's sensor stream or a game's protocol, shows up as "Data". The agent writes a Lua dissector for it from the bytes or a spec, tests it against the open capture and reloads the view, which then decodes the new protocol, with fields you can filter on and show as columns. When rows aren't enough, it writes a panel: a sandboxed page next to the packets that plots, plays or dra