// Systematic approach to debugging REST APIs, HTTP errors, authentication issues, and network problems. Use when the user has API errors, status code issues, timeout problems, or needs help troubleshooting HTTP requests.
OwnPilot official general skill for drafting, editing, restructuring, and reviewing long-form documents, reports, proposals, policies, and documentation. Use when the user asks to create or improve a document.
OwnPilot official general skill for converting rough meeting notes, transcripts, and call summaries into decisions, action items, owners, risks, and follow-ups. Use when the user provides meeting content or asks for notes.
OwnPilot official general skill for creating slide outlines, executive narratives, speaker notes, and presentation critiques. Use when the user asks for slides, a deck, a pitch, or a narrative.
OwnPilot official general skill for turning mixed research material into concise, sourced briefs, comparisons, decisions, and next steps. Use when the user asks to research, compare options, summarize sources, or prepare a recommendation.
OwnPilot official general skill for planning spreadsheet models, analyzing CSV or table data, explaining formulas, checking data quality, and designing reports. Use when the user works with spreadsheet-like data.
Reviews code for quality issues, security vulnerabilities, performance problems, and best practices. Use when the user asks for a code review, wants to improve code quality, or needs feedback on their implementation.
| name | api-debugging |
| description | Systematic approach to debugging REST APIs, HTTP errors, authentication issues, and network problems. Use when the user has API errors, status code issues, timeout problems, or needs help troubleshooting HTTP requests. |
| license | MIT |
| compatibility | Works best with code execution enabled for running curl/fetch commands |
| metadata | {"author":"ownpilot","version":"1.0.0"} |
| allowed-tools | Bash(curl:*) Bash(wget:*) |
You are an expert API debugger. Follow this systematic process when helping troubleshoot API issues.
| Code | Meaning | Common Cause | Fix |
|---|---|---|---|
| 400 | Bad Request | Malformed JSON, missing field | Check request body schema |
| 401 | Unauthorized | Missing/expired token | Refresh auth token |
| 403 | Forbidden | Insufficient permissions | Check API key scopes |
| 404 | Not Found | Wrong URL or deleted resource | Verify endpoint path |
| 405 | Method Not Allowed | GET instead of POST | Check HTTP method |
| 409 | Conflict | Duplicate resource | Check unique constraints |
| 422 | Unprocessable | Validation failed | Check field types/values |
| 429 | Too Many Requests | Rate limited | Add retry with backoff |
| Code | Meaning | Action |
|---|---|---|
| 500 | Internal Server Error | Check server logs, report bug |
| 502 | Bad Gateway | Upstream service down, retry |
| 503 | Service Unavailable | Service overloaded, wait and retry |
| 504 | Gateway Timeout | Increase timeout, check slow queries |
When auth fails (401/403):
Authorization: Bearer <token> vs X-API-Key: <key>)exp)Wait: 1s → 2s → 4s → 8s (max 3-4 retries)
Only retry on: 429, 500, 502, 503, 504
Never retry on: 400, 401, 403, 404
Access-Control-Allow-Origin headerWhen analyzing a failed request, gather:
Endpoint: [METHOD] [URL]
Headers: [Key headers, especially Auth]
Body: [Request payload]
Status: [Response status code]
Response: [Error message or body]
Timing: [How long did it take?]
Context: [When did it start failing? What changed?]