GPTsApp SkillsCodex Reset
Menu
Codex Reset
← Back to results

plugin directory · Use or study

openai-api-troubleshooting

Classify an OpenAI API request failure from concrete transport or API response evidence and identify the next diagnostic action.

openai/pluginsplugins/openai-developers/skills/openai-api-troubleshooting/SKILL.md

Read SKILL.md ↗Open source directory ↗

Before you use it

Input
A redacted status code, error code and message, whether any HTTP response was received, the execution environment and relevant model, project or organization context.
Expected output
A bounded failure class such as transport, authentication, quota, rate limit or access, plus the next check or retry needed before making a stronger conclusion.
Prerequisites
Preserve the exact response evidence without exposing credentials. A transport failure before an API response must stay separate from API-side errors, and two different 429 classes must not be merged. Current links, limits and model guidance require a fresh official documentation check; no API request was made here.

Client setup and runtime behavior are not verified here; client installation is not individually established. The use notes below describe source preparation, inputs and limits.

Publisher documentation, static file observations and environment tests are different kinds of evidence. Runtime behavior has not been observed.

Use this method

Source-based preparation, not an installation or a completed run. Nothing is executed here.

Good fit for
A runtime OpenAI API failure where the user can provide a concrete transport symptom or API response without revealing the secret key.
Not for / limits
Not a key-creation flow, a current API reference or authority to escalate network access. A 401, 403 or 429 alone may be insufficient; source links and named model suggestions can drift and were not independently refreshed here.
Prepare
Capture a redacted error, status, message and response boundary first; note whether the request reached the API before checking keys, billing or model access.
Apply
Route from the strongest evidence: repair the authorized network path before API diagnosis, separate authentication from quota, distinguish quota from ordinary rate limiting, and inspect project or model scope for access errors.
Check
Verify the chosen class with one minimal authorized retry or a current official documentation check, then state remaining ambiguity rather than rotating keys or changing billing without evidence.
Sources read for this note

These exact files were read as text at the displayed commit. Other files and external tools were not reviewed. A repository LICENSE observation does not confirm Skill-specific applicability or dependency rights.

Study the method

Use the eval matrix to compare cases that share an HTTP status but require different actions, especially insufficient quota versus rate limiting and pre-response network failure versus authenticated API responses.

3 files in the observed scope; 0 in scripts/, 1 in references/, 0 in assets/.

Zero files in scripts/ does not mean no execution, network access or file writes. Markdown and other folders may describe or contain executable behavior.

Source version and requirements

Observed
2026-09-07T14:02:40.375Z
Source commit
1e285826e604f66f7208f7ac4dba0fe8341d1f57
Content SHA-256
9fb4e152430c2f0475d1d14ce61b413267d322af9c032f2affb64698ca562662
License
Unknown
Author attribution
Repository owner: openai. Individual authorship is not independently established.

This page describes a pinned source snapshot, not the latest repository state. Changes after this commit have not been reconciled here. A repository license does not necessarily cover external models, datasets or services.

Open current repository ↗
Reference note and manual copy