network-debugging — Claude Code skill: diagnose network failures
Walks your agent through why requests fail, stall or crawl. Useful when the app is slow and the network is the suspect.
npx skills add aj-geddes/useful-ai-prompts --skill network-debugging -a claude-codeWhat network-debugging does
The skill points the agent at the browser's network tab and at how data actually moves. It reads request statuses, initiators, sizes and the waterfall timeline — queueing, DNS, the TCP handshake, SSL/TLS negotiation, time to first byte, content download. That breakdown shows where the time goes.
Four reference guides ship in the references/ directory: browser network tools, common network issues, debugging tools and techniques, and a checklist. The quick start covers the Network tab columns and the timeline stages, plus throttling presets such as Fast 3G. There is nothing to run on its own, and without browser developer tools the skill has nothing to read.
The listed cases are slow loading, failed requests, intermittent connectivity, CORS errors, SSL/TLS problems and API communication failures. An error outside that set is a poor fit.
What it helps with
- pin down which stage of a request eats the time
- trace a CORS failure between frontend and API
- tell an SSL/TLS problem apart from a slow server
- catch connectivity that drops in and out
- see how the app behaves on a throttled connection
Example prompts for the agent
- Figure out why the request to /api/orders fails with a CORS error
- Read the request timeline and tell me where the time goes
- Check how the app behaves under Fast 3G throttling
How to install network-debugging
1Skills CLI (Vercel)
npx skills add aj-geddes/useful-ai-prompts --skill network-debugging -a claude-code2Manually: put the files in place
~/.claude/skills/network-debugging/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/network-debugging/
1Skills CLI (Vercel)
npx skills add aj-geddes/useful-ai-prompts --skill network-debugging -a codex2Manually: put the files in place
.agents/skills/network-debugging/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add aj-geddes/useful-ai-prompts --skill network-debugging -a cursor2Manually: put the files in place
.cursor/skills/network-debugging/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install aj-geddes/useful-ai-prompts network-debugging2Manually: put the files in place
.github/skills/network-debugging/SKILL.md1Skills CLI (Vercel)
npx skills add aj-geddes/useful-ai-prompts --skill network-debugging -a gemini-cli2Platform CLI
gemini skills install https://github.com/aj-geddes/useful-ai-prompts --path skills/network-debuggingManually: put the files in place
.devin/skills/network-debugging/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add aj-geddes/useful-ai-prompts --skill network-debugging -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about network-debugging
How do I install network-debugging in Claude?
Run npx skills add aj-geddes/useful-ai-prompts --skill network-debugging -a claude-code. The skill lands at ~/.claude/skills/network-debugging/SKILL.md.
What does network-debugging do?
It helps the agent diagnose network failures: slow loading, failed requests, intermittent connectivity, CORS errors and SSL/TLS issues. It works from the browser Network tab and the request timeline.
What do I need for it to work?
Access to browser developer tools. Without them there are no statuses, initiators or waterfall timings to read.
Source text
SKILL.md · MIT
--- name: network-debugging description: > Debug network issues using browser tools and network analysis. Diagnose connection problems, latency, and data transmission issues. --- # Network Debugging ## Table of Contents - [Overview](#overview) - [When to Use](#when-to-use) - [Quick Start](#quick-start) - [Reference Guides](#reference-guides) - [Best Practices](#best-practices) ## Overview Network debugging identifies connectivity issues, latency problems, and data transmission errors that impact application performance. ## When to Use - Slow loading times - Failed requests - Intermittent connectivity - CORS errors - SSL/TLS issues - API communication problems ## Quick Start Minimal working example: ```yaml Chrome DevTools Network Tab: Columns: - Name: Request file/endpoint - Status: HTTP status code - Type: Resource type (xhr, fetch, etc) - Initiator: What triggered request - Size: Resource size / transferred size - Time: Total time to complete - Waterfall: Timeline visualization Timeline Breakdown: - Queueing: Waiting in queue - DNS: Domain name resolution - Initial connection: TCP handshake - SSL: SSL/TLS negotiation - Request sent: Time to send request - Waiting (TTFB): Time to first byte - Content Download: Receiving response --- Network Conditions: Throttling Presets: - Fast 3G: 1.6 Mbps down, 750 Kbps up // ... (see reference guides for full implementation) ``` ## Reference Guides Detailed implementations in the `references/` directory: | Guide | Contents | |---|---| | [Browser Network Tools](references/browser-network-tools.md) | Browser Network Tools | | [Common Network Issues](references/common-network-issues.md) | Common Network Issues | | [Debugging Tools & Techniques](references/debugging-tools-techniques.md) | Debugging Tools & Techniques | | [Checklist](references/checklist.md) | Checklist | ## Best Practices ### ✅ DO - Follow established patterns and conventions - Write clean, maintainable code - Add appropriate documentation - Test thoroughly before deploying ### ❌ DON'T - Skip testing or validation - Ignore error handling - Hard-code configuration values
© aj-geddes · MIT · aj-geddes/useful-ai-prompts