Agent skill · Code Review & Quality

network-performance

Expert skill for network performance analysis and optimization. Analyze packet captures, identify network latency bottlenecks, configure TCP tuning parameters, analyze connection pooling behavior, debug TLS handshake performance, and optimize HTTP/2 and HTTP/3 settings.

a5c-aigithub.com/a5c-aiGitHub ↗
claude-codecodexcan modify filesMIT
Install
npx skills add a5c-ai/babysitter --skill network-performance --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 11 KB
Bundled scripts: none
Version: 1.0.0
Declared author: babysitter-sdk
Allowed tools: Bash(*)ReadWriteEditGlobGrepWebFetch
Path: library/specializations/performance-optimization/skills/network-performance/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,642
Language: JavaScript

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# network-performance You are **network-performance** - a specialized skill for network performance analysis and optimization. This skill provides expert capabilities for identifying and resolving network-related performance bottlenecks across TCP/IP, TLS, HTTP/2, and HTTP/3 protocols. ## Overview This skill enables AI-powered network performance operations including: - Analyzing packet captures with tcpdump/Wireshark patterns - Identifying network latency bottlenecks - Configuring TCP tuning parameters (buffers, congestion control) - Analyzing connection pooling behavior - Debugging TLS handshake performance - Optimizing HTTP/2 and HTTP/3 settings - Implementing network compression strategies ## Prerequisites - tcpdump, tshark (Wireshark CLI) - ss, netstat, ip utilities - curl with HTTP/2 and HTTP/3 support - Optional: iperf3, mtr, traceroute - Root/admin access for packet capture ## Capabilities ### 1. TCP Performance Analysis Analyze and optimize TCP performance: ```bash # Capture TCP packets for analysis tcpdump -i eth0 -nn -tttt -s 0 \ 'tcp port 443 and host api.example.com' \ -w capture.pcap -c 10000 # Analyze with tshark tshark -r capture.pcap -q -z io,stat,1,"tcp" # Extract

What's inside
Steps it walks through
  1. Overview
  2. Prerequisites
  3. Capabilities
  4. 1. TCP Performance Analysis
  5. 2. TCP Tuning Configuration
  6. 3. Connection Pooling Analysis
  7. 4. TLS Handshake Optimization
  8. 5. HTTP/2 Optimization
  9. 6. HTTP/3 (QUIC) Optimization
  10. 7. Network Latency Analysis
  11. 8. Bandwidth and Throughput Testing
  12. MCP Server Integration
  13. Best Practices
  14. TCP Tuning
Ships with 1 file
  • README.md
Commands it runs
Capture TCP packets for analysis
tcpdump -i eth0 -nn -tttt -s 0 \
Analyze with tshark
tshark -r capture.pcap -q -z io,stat,1,"tcp"
Extract TCP RTT statistics
tshark -r capture.pcap \
awk '{sum+=$1; count++} END {print "Avg RTT:", sum/count*1000, "ms"}'
Check for retransmissions
tshark -r capture.pcap -q -z expert,error
tshark -r capture.pcap -Y "tcp.analysis.retransmission" | wc -l
More from babysitter
All skills →
About this skill
What does the network-performance skill do?

Expert skill for network performance analysis and optimization. Analyze packet captures, identify network latency bottlenecks, configure TCP tuning parameters, analyze connection pooling behavior, debug TLS handshake performance, and optimize HTTP/2 and HTTP/3 settings.

How do I install it?

Run `npx skills add a5c-ai/babysitter --skill network-performance --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From a5c-ai/babysitter, a repository with 1,642 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going