openai-api-troubleshooting

Use when an OpenAI API request fails or the user asks what an error means, including blocked access to api.openai.com, 401 invalid_api_key, missing OPENAI_API_KEY, 429 insufficient_quota, 429 rate_limit_exceeded, or 403 model_not_found. Classify the failure, name the next step, route credential setup to openai-platform-api-key, and current guidance to openai-docs.

Ir para a instalação

Repositório: openai/openai-developers-for-cursor
Última atividade na origem: 23 de junho de 2026 às 19:38
Idioma detectado do SKILL.md: inglês
Estrelas: 5
Forks: 2

Opções de instalação

Por padrão, está selecionado o prompt que primeiro revisa a origem. Você pode mudar para um comando direto ou baixar uma cópia local.

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.

npx skills add https://github.com/openai/openai-developers-for-cursor --skill openai-api-troubleshooting

O comando permanece em uma só linha. Role horizontalmente para revisá-lo antes de copiar.

Prefere uma cópia local? Baixe os arquivos disponíveis atualmente no SkillsMP.

Revise os arquivos de origem

Leia o SKILL.md e os arquivos complementares exibidos pelo SkillsMP antes de decidir se vai instalar.

SKILL.md

Instruções da origem · Visualização somente leitura

Voltar à pesquisa Voltar à instalação

OpenAI API Troubleshooting

Use this for runtime OpenAI API failures after a request has already been made. Keep key setup in openai-platform-api-key and current guidance in openai-docs.

Routing

Sandboxed or blocked outbound network access

Treat DNS errors, connection timeouts, connection resets, or inability to reach api.openai.com before any API response as transport problems first.
If the failure came from a sandboxed or restricted run, explicitly recommend retrying the actual request with network access enabled or outside that restriction; only classify API-side auth, quota, rate-limit, or model access after a concrete OpenAI response exists.

Authentication or missing-key errors

Route 401, invalid_api_key, missing OPENAI_API_KEY, or malformed-key cases to authentication.
If a key must be created or configured, explicitly hand off to openai-platform-api-key; do not stop at generic "create a fresh key" advice.

Quota or credit exhaustion

Treat insufficient_quota, "current quota", "billing quota", "run out of credits", or "no balance left" as billing/quota exhaustion, not ordinary throttling.
For exhausted credits, prompt the user to add credits and include Add API credits. Do not purchase credits or change billing settings.
Link usage caps to https://platform.openai.com/settings/organization/limits.
If ambiguous, say it may be credits or a spend limit and consult openai-docs; when useful, note that ChatGPT subscriptions and API billing are separate.

Rate limits

Route rate_limit_exceeded, requests-per-minute, tokens-per-minute, or retry-after guidance without quota language to throttling.
Recommend pacing, batching, exponential backoff, or lower concurrency; do not suggest buying credits unless the error also indicates quota exhaustion.

Model, project, or organization access

Treat 403, model_not_found, org/project mismatch, or permission failures as reached-OpenAI-but-not-authorized cases.
Check the model, project, organization, and key scope before guessing.

Rules

Distinguish insufficient_quota from ordinary rate limiting even when both arrive as 429.

Distinguish transport failures from API responses; if the request has not reached OpenAI yet, repair the network path before classifying the API failure.

Prefer the concrete API error code and message over generic heuristics.

Keep user-facing answers short: likely class, reason, next action.

Do not rotate or create keys here.

Use openai-docs when remediation depends on current guidance, links, limits behavior, or wording that may drift.