What problem does it solve?
When an OpenAI API request fails, error messages like 401, 403, or 429 can be ambiguous, and developers often misdiagnose quota exhaustion as rate limiting or blame credentials when the real issue is blocked sandbox networking. This Skill classifies the actual failure class and points to the correct next action.
Core Features & Use Cases
- Failure Classification: Distinguishes transport failures (DNS errors, timeouts, connection resets) from API-side errors such as authentication, quota exhaustion, rate limiting, and model or project access issues.
- Sandbox Escalation Guidance: Detects when a Codex sandbox blocks outbound network access and directs rerunning the actual API request with escalated permissions before further diagnosis.
- Precise 429 Routing: Separates
insufficient_quota (billing or credits) from ordinary rate_limit_exceeded, linking to the correct billing or limits settings page.
- Use Case: Your API call returns
429 insufficient_quota inside a Codex session. The Skill identifies credit exhaustion, links to the organization billing page, and avoids suggesting backoff strategies that would not help.
Quick Start
Ask the assistant to diagnose why your OpenAI API request is failing and what to do next.