api-debugging

Diagnose API errors including authentication failures, routing problems, and integration issues.

Updated Sep 14, 2026
One-click install
npx skills add https://github.com/Lawrence908/chiron --skill api-debugging-lawrence908
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: api-debugging
Source: https://github.com/Lawrence908/chiron/tree/main/plugins/dev/skills/api-debugging
Command: npx skills add https://github.com/Lawrence908/chiron --skill api-debugging-lawrence908

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? API failures like 401 errors, CORS blocks, webhook delivery failures, and OAuth token issues are time-consuming to isolate. This Skill provides a systematic debugging workflow that pinpoints root causes instead of guessing at fixes. ## Core Features & Use Cases - Structured Debugging Workflow: A 10-step procedure covering reproduction, status code analysis, auth verification, log review, and minimal-request isolation. - OAuth and JWT Diagnostics: Concrete commands to decode JWTs, check expiration claims, validate redirect URIs, and test token refresh flows. - Common Issue Playbook: Pre-mapped fixes for rate limiting, CORS errors, webhook signature failures, and scope mismatches. - Use Case: Your endpoint returns 401 Unauthorized despite a valid-looking token. The Skill walks you through decoding the JWT, checking the exp claim, testing with curl, and reviewing server logs to find the exact cause. ## Quick Start Debug why my API endpoint returns a 401 Unauthorized error even though my bearer token appears valid.

Frequently Asked Questions about api-debugging

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug a 401 Unauthorized API error?▼

Start by decoding the JWT to inspect its header and payload, then check the exp claim for expiration. Test the request with curl using the Authorization: Bearer header, review server logs for 401 entries, and verify signature, issuer, and audience validation.

How to fix OAuth token refresh failures?▼

Verify the redirect_uri matches exactly including trailing slashes, validate the token response contains access_token, refresh_token, and expires_in, and test the refresh flow before the access token expires. Also confirm the state parameter is validated for CSRF protection.

Why does my API request fail with CORS errors?▼

CORS errors occur when the server's allowed origins, credentials, or headers do not match the client's cross-origin request. Verify the Access-Control-Allow-Origin configuration and ensure required headers and methods are permitted on the server.

How do I debug webhook delivery failures?▼

Check that webhook signatures are validated on receipt and that retry logic is implemented for failed deliveries. Review delivery logs on the provider side and confirm the receiving endpoint returns the expected acknowledgment status code.

What causes API rate limiting errors and how to handle them?▼

Rate limiting returns 429 responses when request quotas are exceeded. Inspect X-RateLimit-* response headers to understand limits and remaining quota, then implement exponential backoff and request throttling in the client.