What problem does it solve? Support engineers and integrators waste hours on vague API answers and misdiagnosed errors. This Skill ensures every integration answer includes a working request and every error diagnosis starts from the actual status code rather than guesswork. ## Core Features & Use Cases - Complete request answers: Every response includes the method and path, individually named required headers, a full example body, the success response shape, and what a refusal looks like. - Status-code-driven diagnosis: Maps 401, 403, 404, 422, and 429 responses to their likely causes, including the distinction between a missing row and the wrong tenant context on a 404. - Evidence-based troubleshooting: Requires the full request with secrets redacted, the complete response with headers, and the timestamp before diagnosing. - Use Case: A customer reports a 403 on an endpoint they believe they can access. The Skill identifies that they are authenticated but not permitted, and names the specific permission they need. ## Quick Start Help me diagnose why my API request returns a 422 error and show me the correct request format.
