network-debug
Skill5 starsChanged 5 months agoMITView on GitHub
Investigating API failures, DNS issues, and connection timeouts
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 11
When external APIs or microservices return 5xx/4xx errors or timeouts.
- Distinctive: line 12
When facing DNS resolution issues, TLS handshake failures, or CORS errors.
- Distinctive: line 13
When debugging load balancer or reverse proxy routing.
- Distinctive: line 16
Curl & Ping: Use basic tools to ensure reachability before debugging application code.
- Distinctive: line 18
Timeouts & Retries: Verify that both read and connect timeouts are explicitly set, and retry logic is idempotent.
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Network Debugging Skill
This skill focuses on tracing requests across distributed networks, resolving timeouts, and understanding protocol errors.
When to use this skill
- When external APIs or microservices return 5xx/4xx errors or timeouts.
- When facing DNS resolution issues, TLS handshake failures, or CORS errors.
- When debugging load balancer or reverse proxy routing.
Guidelines
- Curl & Ping: Use basic tools to ensure reachability before debugging application code.
- Trace IDs: Utilize distributed tracing (OpenTelemetry, Jaeger) to identify exactly where a request failed in a multi-service architecture.
- Timeouts & Retries: Verify that both read and connect timeouts are explicitly set, and retry logic is idempotent.
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- franco-bianco/claude-skills★ 4same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository38 other files it gives its agents.
- AGENTS.mdAGENTS.md
- codex/AGENTS.mdAGENTS.md
- claude/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- fastapiSkill
- rustSkill
- backend-codeSkill
- frontend-codeSkill
- javascript-codeSkill
- java-codeSkill
- python-codeSkill
- codeSkill
- crash-analysisSkill
- memory-debugSkill
- performance-debugSkill
- debugSkill
- argo-cdSkill
- dockerSkill
- github-actionsSkill
- gitlab-ciSkill
- jenkinsSkill
- kubernetesSkill
- devopsSkill
- terraformSkill
- nextjsSkill
- react-nativeSkill
- api-design-planSkill
- architecture-planSkill
- database-planSkill
- security-planSkill
- planSkill
- e2e-testSkill
- integration-testSkill
- testSkill
- tddSkill
- unit-testSkill
- smart-contractsSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.