← ClaudeAtlas

network-protocollisted

Use whenever the user wants to design, implement, review, or debug a network protocol or client/server wire communication over TCP, UDP, QUIC, TLS, WebSockets, Unix domain, or raw sockets — framing, binary/wire formats, RPC, handshakes, message formats. Also use to capture and analyze protocol traffic on the wire (tcpdump, Wireshark/tshark, scapy, custom dissectors); to deploy or troubleshoot a protocol in cloud and orchestrated networks (AWS VPC, GCP networking, Kubernetes and CNI, load balancers, MTU, NAT); and as a study aid for networking certifications (CCNA, subnetting, OSI/TCP-IP, routing and switching). Trigger on debugging symptoms too: messages merged or split, partial reads/writes, hangs that never time out, intermittent corruption, works-on-localhost-fails-over-the-network, undetected connection drops, or memory blowups under load. Do NOT use it for pure HTTP-REST-API calls with an existing client library or front-end fetch(), where no custom protocol is involved.
TheFoxOverflow/network-protocol-skill · ★ 6 · DevOps & Infrastructure · score 76
Install: claude install-skill TheFoxOverflow/network-protocol-skill
# Network protocol design & implementation ## What this skill is for Designing and implementing protocols correctly is hard for one specific reason: **the failure modes are invisible in the happy path.** Code that merges two messages into one buffer, trusts a length field, or never sets a timeout will pass review, pass unit tests, and demo perfectly on `localhost` — then corrupt data or hang the moment it meets a real network with partial reads, slow peers, reordered packets, or a malicious client. This skill front-loads those failure modes. It contains a catalog of the bugs that actually bite, the design decisions that avoid whole bug classes, defensive implementation patterns, a security model for untrusted peers, a testing strategy that *provokes* the failures instead of hoping they don't happen, the operational layer that makes a correct protocol actually production-ready, and a final review checklist. There is also a production-grade reference library with a full test suite. The goal is a result that is genuinely production-ready, not merely correct on the happy path: framed and bounded, defended against hostile peers, observable, gracefully degrading under load, and safe to deploy and evolve. Beyond designing and building a protocol, this skill also helps you **observe** one on the wire (packet capture and analysis with tcpdump, Wireshark, and Python), **deploy** one into real cloud and Kubernetes networks (where load balancers, NAT, MTU, and firewalls change the r