Network Debug
Inspect HTTP traffic captured by PowHTTP MCP proxy. Use when fixing request mismatches in existing code or building new API flows from browser traffic.
Install
npx skills add franco-bianco/claude-skills --skill network-debuggit clone --depth 1 https://github.com/franco-bianco/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/network-debug ~/.claude/skills/network-debugPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Network Debug
Inspect HTTP traffic captured by PowHTTP proxy. Two primary use cases: fixing existing request flows and building new ones from scratch.
See [tool-reference.md](references/tool-reference.md) for tool documentation and [token-optimization.md](references/token-optimization.md) for token optimization.
## Verify PowHTTP is Running
```text
powhttp_session_active()
```
## Workflow 1: Fix Existing Code
When a Go client request fails or returns unexpected results, compare it against browser traffic in PowHTTP to find the mismatch.
### 1. Capture both request flows
Run the same action in the browser and through the Go client while PowHTTP captures. Find entries from each source:
```text
powhttp_search_entries(filters: {host: "*.example.com", process_name: "chrome"}, limit: 20)
powhttp_search_entries(filters: {host: "*.example.com", process_name: "server"}, limit: 20)
```
### 2. Compare the request sequence
Use `powhttp_trace_flow` on each flow's first request to see the full chain. Compare:
- **Request order** — both flows must make the same requests in the same sequence. A reordered request often causes auth failures or missing cookies downstream.
- **Request count** — if the Go client skips a request the browser makes (e.g., a token refresh, a session init), downstream requests may fail due to missing state.
### 3. Compare individual requests
For each corresponding pair of requests, use `powhttp_diff_entries`:Details
- Skill name
network-debug- Repository
- franco-bianco/claude-skills
- Path
network-debug/SKILL.md- License
- MIT
- Repo updated
- 7 March 2026
FAQ
What does the Network Debug skill do?
Inspect HTTP traffic captured by PowHTTP MCP proxy. Use when fixing request mismatches in existing code or building new API flows from browser traffic.
How do I install the Network Debug skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add franco-bianco/claude-skills --skill network-debug. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Network Debug popular?
It lives in franco-bianco/claude-skills, which has 5 GitHub stars and 0 forks.
Related skills
Browser Navigate
5franco-bianco/claude-skills
Control Chrome via DevTools MCP to visit pages, interact with elements, and extract content. Use when navigating websites, filling forms, taking screenshots, or automating browser interactions.
Recon
5franco-bianco/claude-skills
Systematically discover alternative endpoints, bypasses, and undocumented access paths on a target platform. Use after the normal flow works to find simpler or more efficient approaches.
Cloudflare Architecture
9zllovesuki/cloudflare-agent-skills
Choose Cloudflare Developer Platform primitives and architecture shapes before writing code. Use for Cloudflare Workers, Durable Objects, D1, R2, Queues, Workflows, Containers, Realtime, Workers AI, Vectorize, AI Search, Agents, cost, limits, and migration decisions.
Architecture
9sukirman1901/frontend-expert
Frontend structure — feature folders, state ownership, server/client boundary, when not to add a global store. Use for "arsitektur FE", folder structure, refactor large UI, state management choice, or modularizing an app.
Cost Optimization
9zllovesuki/cloudflare-agent-skills
Optimize Cloudflare Developer Platform costs for Workers CPU vs wall time, D1 operations, KV reads/writes, R2 storage/egress, Durable Object hotspots, Queues, Workflows, Workers AI tokens, and architecture-level trade-offs. Use during design and production reviews.
Anti Slop Code
9sukirman1901/frontend-expert
Detect and fix AI-generated frontend implementation slop: isolated helpers that ignore other modules, needless useEffect, type lies, empty wrappers, and boilerplate error handling that misses field edge cases. Trigger for “kode terasa AI”, “rapikan kode”, “dampak ke modul lain”, “edge case”, “error handling generik”, “too many useEffect”, or “over-engineered”. Visual slop stays on anti-slop-design; copy stays on content-design.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.