[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AC6XMX7SVT6EZNVKCVGR22":3,"skill-same:01M6AC6XMX7SVT6EZNVKCVGR22":60},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":28,"publishedAt":33,"linkOnly":34,"markdownContent":35,"markdownBody":36,"frontMatter":37,"refName":38,"commitSha":39,"skillDirectory":40,"forksCount":41,"repositoryHtmlUrl":42,"repositoryHomepageUrl":6,"ownerHtmlUrl":43,"ownerBlogUrl":44,"ownerDescription":6,"updatedAt":45,"install":46,"resources":59},"01M6AC6XMX7SVT6EZNVKCVGR22","openai-api-troubleshooting",null,"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.","openai\u002Fopenai-developers-for-cursor","openai","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F14957082?v=4","01M6AC29YGCR4S2NTJFV0G8B81","OpenAI","01M6AC6NVP3PRMD1JT63NPWBPP",13,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fopenai\u002Fopenai-developers-for-cursor\u002Fblob\u002Fmain\u002Fskills\u002Fopenai-api-troubleshooting\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[9,29,30,31,32],"openai api","openai api troubleshooting","docs","setup","2026-11-10 10:12:30",false,"---\nname: openai-api-troubleshooting\ndescription: 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.\n---\n\n# OpenAI API Troubleshooting\n\nUse 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`.\n\n## Routing\n\n1. Sandboxed or blocked outbound network access\n   - Treat DNS errors, connection timeouts, connection resets, or inability to reach `api.openai.com` before any API response as transport problems first.\n   - 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.\n\n2. Authentication or missing-key errors\n   - Route `401`, `invalid_api_key`, missing `OPENAI_API_KEY`, or malformed-key cases to authentication.\n   - 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.\n\n3. Quota or credit exhaustion\n   - Treat `insufficient_quota`, \"current quota\", \"billing quota\", \"run out of credits\", or \"no balance left\" as billing\u002Fquota exhaustion, not ordinary throttling.\n   - For exhausted credits, prompt the user to add credits and include [Add API credits](https:\u002F\u002Fplatform.openai.com\u002Fsettings\u002Forganization\u002Fbilling\u002Foverview). Do not purchase credits or change billing settings.\n   - Link usage caps to `https:\u002F\u002Fplatform.openai.com\u002Fsettings\u002Forganization\u002Flimits`.\n   - 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.\n\n4. Rate limits\n   - Route `rate_limit_exceeded`, requests-per-minute, tokens-per-minute, or retry-after guidance without quota language to throttling.\n   - Recommend pacing, batching, exponential backoff, or lower concurrency; do not suggest buying credits unless the error also indicates quota exhaustion.\n\n5. Model, project, or organization access\n   - Treat `403`, `model_not_found`, org\u002Fproject mismatch, or permission failures as reached-OpenAI-but-not-authorized cases.\n   - Check the model, project, organization, and key scope before guessing.\n\n## Rules\n\n- Distinguish `insufficient_quota` from ordinary rate limiting even when both arrive as `429`.\n- Distinguish transport failures from API responses; if the request has not reached OpenAI yet, repair the network path before classifying the API failure.\n- Prefer the concrete API error code and message over generic heuristics.\n- Keep user-facing answers short: likely class, reason, next action.\n- Do not rotate or create keys here.\n- Use `openai-docs` when remediation depends on current guidance, links, limits behavior, or wording that may drift.\n","# OpenAI API Troubleshooting\n\nUse 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`.\n\n## Routing\n\n1. Sandboxed or blocked outbound network access\n   - Treat DNS errors, connection timeouts, connection resets, or inability to reach `api.openai.com` before any API response as transport problems first.\n   - 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.\n\n2. Authentication or missing-key errors\n   - Route `401`, `invalid_api_key`, missing `OPENAI_API_KEY`, or malformed-key cases to authentication.\n   - 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.\n\n3. Quota or credit exhaustion\n   - Treat `insufficient_quota`, \"current quota\", \"billing quota\", \"run out of credits\", or \"no balance left\" as billing\u002Fquota exhaustion, not ordinary throttling.\n   - For exhausted credits, prompt the user to add credits and include [Add API credits](https:\u002F\u002Fplatform.openai.com\u002Fsettings\u002Forganization\u002Fbilling\u002Foverview). Do not purchase credits or change billing settings.\n   - Link usage caps to `https:\u002F\u002Fplatform.openai.com\u002Fsettings\u002Forganization\u002Flimits`.\n   - 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.\n\n4. Rate limits\n   - Route `rate_limit_exceeded`, requests-per-minute, tokens-per-minute, or retry-after guidance without quota language to throttling.\n   - Recommend pacing, batching, exponential backoff, or lower concurrency; do not suggest buying credits unless the error also indicates quota exhaustion.\n\n5. Model, project, or organization access\n   - Treat `403`, `model_not_found`, org\u002Fproject mismatch, or permission failures as reached-OpenAI-but-not-authorized cases.\n   - Check the model, project, organization, and key scope before guessing.\n\n## Rules\n\n- Distinguish `insufficient_quota` from ordinary rate limiting even when both arrive as `429`.\n- Distinguish transport failures from API responses; if the request has not reached OpenAI yet, repair the network path before classifying the API failure.\n- Prefer the concrete API error code and message over generic heuristics.\n- Keep user-facing answers short: likely class, reason, next action.\n- Do not rotate or create keys here.\n- Use `openai-docs` when remediation depends on current guidance, links, limits behavior, or wording that may drift.\n",{"name":5,"description":7},"main","9120f1f6bb47964651ab822e24b4f358e3638ae3","skills\u002Fopenai-api-troubleshooting",7,"https:\u002F\u002Fgithub.com\u002Fopenai\u002Fopenai-developers-for-cursor","https:\u002F\u002Fgithub.com\u002Fopenai","https:\u002F\u002Fopenai.com\u002F","2026-11-03 02:58:28",{"source":8,"skillName":5,"commands":47,"prompt":57,"zipAvailable":58},[48,51,54],{"tool":49,"command":50},"npx","npx skills add openai\u002Fopenai-developers-for-cursor --skill openai-api-troubleshooting",{"tool":52,"command":53},"bunx","bunx skills add openai\u002Fopenai-developers-for-cursor --skill openai-api-troubleshooting",{"tool":55,"command":56},"pnpm","pnpm dlx skills add openai\u002Fopenai-developers-for-cursor --skill openai-api-troubleshooting","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fopenai\u002Fopenai-developers-for-cursor\u002Fblob\u002Fmain\u002Fskills\u002Fopenai-api-troubleshooting\u002FSKILL.md",true,[],[61,89,115,131,145],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":69,"publishedAt":33},"01M6AC7153A1XFEDJXYNRQSCP1","openai-platform-api-key","Use when Cursor is asked to build, run, test, debug, or configure an OpenAI-backed or provider-unspecified AI app, UI, script, CLI, generator, or tool, especially requests phrased only as \"using AI\" or generators driven by forms\u002Fuser input; also use for OPENAI_API_KEY or sk-proj setup. Do not gate model or prompt migrations that can proceed with source edits and offline validation. Otherwise treat this as the credential gate: inspect safely, ask reuse-vs-new before API work, guide manual local setup when needed, verify presence, and never expose plaintext.","https:\u002F\u002Fgithub.com\u002Fopenai\u002Fopenai-developers-for-cursor\u002Fblob\u002Fmain\u002Fskills\u002Fopenai-platform-api-key\u002FSKILL.md",[67,68],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},[9,70,71,72,73,74,75,76,77,78,79,80,81,82,83,84,85,86,87,88],"openai platform api key","api","platform","input","as","guide","ui","work","cli","run","offline","forms","app","never","model","local","only","configure","ask",{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":98,"publishedAt":33},"01M6AC6ZDADZBE7S8SACF903BJ","openai-docs","Use whenever the user asks anything about OpenAI products, APIs, models, or SDKs — including factual lookups (\"what is the newest model\", \"does X support Y\"), build\u002Fcoding requests (\"write a script using the Responses API\"), latest\u002Fcurrent\u002Fdefault-model prompting guidance, model migrations, and citation requests. Invoke before calling any openaiDeveloperDocs MCP tool.","https:\u002F\u002Fgithub.com\u002Fopenai\u002Fopenai-developers-for-cursor\u002Fblob\u002Fmain\u002Fskills\u002Fopenai-docs\u002FSKILL.md",[95],{"categoryNo":96,"categoryName":97,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[99,31,9,100,101,102,103,104,105,106,107,108,71,109,110,84,111,112,113,114],"openai docs","migrations","build","models","about","write","script","guidance","responses api","coding","MCP","support","tool","default","calling","use",{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":122,"publishedAt":33},"01M6AC6VDFEBYF8TBM4FM09KWD","chatgpt-app-submission","Use when a developer needs a ChatGPT Apps submission import file from an MCP server. Inspect the implementation, generate chatgpt-app-submission.json with app info, tool-hint justifications, positive and negative test cases, then report review findings and outputSchema warnings.","https:\u002F\u002Fgithub.com\u002Fopenai\u002Fopenai-developers-for-cursor\u002Fblob\u002Fmain\u002Fskills\u002Fchatgpt-app-submission\u002FSKILL.md",[121],{"categoryNo":96,"categoryName":97,"taxonomyType":21,"taxonomyTypeDesc":22},[123,124,125,109,126,127,128,129,130],"chatgpt app submission","chatgpt","test","chatgpt apps","generate","mcp server","report","review",{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":138,"publishedAt":33},"01M6AC6S2BGKFHQP4QW3AFNSTD","build-chatgpt-app","Use when the user explicitly wants a ChatGPT App, Apps SDK project, MCP server plus widget UI, ChatGPT-compatible tool UI, or submission\u002Fdeployment work for that surface. Build, scaffold, refactor, or troubleshoot those projects from Cursor, consult openai-docs before generating code, and use openai-platform-api-key before any app path that requires live OpenAI API credentials.","https:\u002F\u002Fgithub.com\u002Fopenai\u002Fopenai-developers-for-cursor\u002Fblob\u002Fmain\u002Fskills\u002Fbuild-chatgpt-app\u002FSKILL.md",[137],{"categoryNo":96,"categoryName":97,"taxonomyType":21,"taxonomyTypeDesc":22},[124,139,109,9,29,31,128,140,141,142,143,144],"build chatgpt app","sdk","code","deployment","scaffold","troubleshoot",{"skillNo":146,"name":147,"nameZh":6,"description":148,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":149,"categories":150,"keywords":151,"publishedAt":33},"01M6AC6QD2NYKG0A81BXFK22TA","agents-sdk","Use when the user wants to build, adapt, run, or evaluate an OpenAI Agents SDK app from Cursor. Prefer a docs-first workflow and route API credential decisions through openai-platform-api-key before API-backed work.","https:\u002F\u002Fgithub.com\u002Fopenai\u002Fopenai-developers-for-cursor\u002Fblob\u002Fmain\u002Fskills\u002Fagents-sdk\u002FSKILL.md",[],[152,140,9,31,153,79],"agents sdk","workflow"]