[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AC6ZDADZBE7S8SACF903BJ":3,"skill-same:01M6AC6ZDADZBE7S8SACF903BJ":70},{"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":23,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":51,"repositoryHtmlUrl":52,"repositoryHomepageUrl":6,"ownerHtmlUrl":53,"ownerBlogUrl":54,"ownerDescription":6,"updatedAt":55,"install":56,"resources":69},"01M6AC6ZDADZBE7S8SACF903BJ","openai-docs",null,"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.","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-docs\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,9,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"docs","openai docs","script","MCP","about","calling","build","default","migrations","guidance","models","use","write","coding","model","tool","api","responses api","support","2026-11-10 10:12:30",false,"---\nname: openai-docs\ndescription: 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.\n---\n\n# OpenAI Docs\n\nUse the Cursor-configured OpenAI Docs MCP server at `https:\u002F\u002Fdevelopers.openai.com\u002Fmcp?source=cursor` first for current OpenAI developer guidance.\n\n## API key setup\n\nFor model and prompt migrations, missing credentials block only the live call. They do not block requested migration source or configuration edits, documentation retrieval, or offline, mocked, static, fixture-based, or syntax validation. For other requests to build, run, configure, debug, or implement API-backed functionality, use `openai-platform-api-key` first when available.\n\nFor model migration or prompting-guidance requests, retrieve the relevant current guidance before any live-call credential check. Continue with requested source edits and offline validation when no API key is available; skip only validation that actually sends a live API request, and say that it was skipped.\n\n## Model guidance routing\n\nClassify the model request before inspecting the project or checking credentials:\n\n- **Dynamic target:** For latest, current, newest, recommended, default, flagship, or otherwise unspecified model selection, prompting, or migration, fetch `https:\u002F\u002Fdevelopers.openai.com\u002Fapi\u002Fdocs\u002Fguides\u002Flatest-model.md`. Read its `latestModelInfo` metadata. For migrations or prompting guidance, resolve the exact `migrationGuide` and `promptingGuide` paths against `https:\u002F\u002Fdevelopers.openai.com` and fetch those exact URLs. Treat the metadata values as opaque; do not derive or substitute another route.\n- **Explicit target:** Preserve the requested model and fetch `https:\u002F\u002Fdevelopers.openai.com\u002Fapi\u002Fdocs\u002Fguides\u002Flatest-model?model=\u003Crequested-model>`. For example, use `https:\u002F\u002Fdevelopers.openai.com\u002Fapi\u002Fdocs\u002Fguides\u002Flatest-model?model=gpt-5.6` for GPT-5.6 and `https:\u002F\u002Fdevelopers.openai.com\u002Fapi\u002Fdocs\u002Fguides\u002Flatest-model?model=gpt-5.3-codex` for `gpt-5.3-codex`. Do not replace the explicit target with the current model.\n\nIf an exact URL is unavailable or lacks substantive content, retry it once through Docs MCP, then run a compact Docs MCP search for that exact model or page. If necessary, fall back only to official OpenAI domains such as `developers.openai.com` and `platform.openai.com`. Do not widen to Slack, internal docs, private repositories, or historical launch artifacts.\n\nIf current-model metadata or an explicit model guide still cannot be retrieved, say what could not be verified and return bounded uncertainty. Do not infer current model facts, migration steps, limits, pricing, availability, parameters, or capabilities from static knowledge.\n\n## General workflow\n\n1. Use the OpenAI Docs MCP tools exposed by the configured `openaiDeveloperDocs` server.\n2. Start general lookup with a compact, title-like search query of 2-6 essential terms. If search is noisy, narrow it.\n3. When a plausible official docs URL is known, fetch it through Docs MCP before web fallback.\n4. For API schemas, parameters, or required fields, use `get_openapi_spec` when available alongside the guide.\n5. Use `list_openai_docs` only when no clear query or URL exists.\n6. Fetch the exact page or section needed before answering.\n7. Cite retrieved official sources for links, quotes, and precise claims.\n\n## Migration rules\n\n- Keep upgrades behavior-preserving. Update active OpenAI model defaults, directly related prompts, and only the registries, routing, pricing, capability, or picker surfaces the user placed in scope.\n- Preserve multi-model cost, latency, and quality roles. Do not collapse a router or picker into one flagship model.\n- Leave historical docs, examples, eval baselines, fixtures, provider comparisons, intentionally pinned fallbacks, and ambiguous older usage unchanged unless explicitly requested.\n- Keep SDK, tooling, IDE, plugin, shell, auth, and provider-environment migrations out of a model-and-prompt upgrade unless explicitly requested.\n- If a safe change requires endpoint or schema rewiring, tool-handler changes, state changes, or another compatibility migration outside scope, report the exact blocker or ask for confirmation.\n\n## Validation\n\nAfter changes, run targeted tests for changed behavior and the most relevant type, lint, build, or smoke checks available. For model migrations, verify every active default surface in scope and exercise representative requests or evals. If validation cannot run, state why and name the next best check.\n\n## Rules\n\n- Treat live OpenAI documentation as the source of truth; never use bundled model guidance as a fallback.\n- Preserve explicit model targets.\n- Prefer concise summaries over long excerpts.\n- If sources conflict, state the difference. If evidence is missing, narrow the answer instead of guessing.\n","# OpenAI Docs\n\nUse the Cursor-configured OpenAI Docs MCP server at `https:\u002F\u002Fdevelopers.openai.com\u002Fmcp?source=cursor` first for current OpenAI developer guidance.\n\n## API key setup\n\nFor model and prompt migrations, missing credentials block only the live call. They do not block requested migration source or configuration edits, documentation retrieval, or offline, mocked, static, fixture-based, or syntax validation. For other requests to build, run, configure, debug, or implement API-backed functionality, use `openai-platform-api-key` first when available.\n\nFor model migration or prompting-guidance requests, retrieve the relevant current guidance before any live-call credential check. Continue with requested source edits and offline validation when no API key is available; skip only validation that actually sends a live API request, and say that it was skipped.\n\n## Model guidance routing\n\nClassify the model request before inspecting the project or checking credentials:\n\n- **Dynamic target:** For latest, current, newest, recommended, default, flagship, or otherwise unspecified model selection, prompting, or migration, fetch `https:\u002F\u002Fdevelopers.openai.com\u002Fapi\u002Fdocs\u002Fguides\u002Flatest-model.md`. Read its `latestModelInfo` metadata. For migrations or prompting guidance, resolve the exact `migrationGuide` and `promptingGuide` paths against `https:\u002F\u002Fdevelopers.openai.com` and fetch those exact URLs. Treat the metadata values as opaque; do not derive or substitute another route.\n- **Explicit target:** Preserve the requested model and fetch `https:\u002F\u002Fdevelopers.openai.com\u002Fapi\u002Fdocs\u002Fguides\u002Flatest-model?model=\u003Crequested-model>`. For example, use `https:\u002F\u002Fdevelopers.openai.com\u002Fapi\u002Fdocs\u002Fguides\u002Flatest-model?model=gpt-5.6` for GPT-5.6 and `https:\u002F\u002Fdevelopers.openai.com\u002Fapi\u002Fdocs\u002Fguides\u002Flatest-model?model=gpt-5.3-codex` for `gpt-5.3-codex`. Do not replace the explicit target with the current model.\n\nIf an exact URL is unavailable or lacks substantive content, retry it once through Docs MCP, then run a compact Docs MCP search for that exact model or page. If necessary, fall back only to official OpenAI domains such as `developers.openai.com` and `platform.openai.com`. Do not widen to Slack, internal docs, private repositories, or historical launch artifacts.\n\nIf current-model metadata or an explicit model guide still cannot be retrieved, say what could not be verified and return bounded uncertainty. Do not infer current model facts, migration steps, limits, pricing, availability, parameters, or capabilities from static knowledge.\n\n## General workflow\n\n1. Use the OpenAI Docs MCP tools exposed by the configured `openaiDeveloperDocs` server.\n2. Start general lookup with a compact, title-like search query of 2-6 essential terms. If search is noisy, narrow it.\n3. When a plausible official docs URL is known, fetch it through Docs MCP before web fallback.\n4. For API schemas, parameters, or required fields, use `get_openapi_spec` when available alongside the guide.\n5. Use `list_openai_docs` only when no clear query or URL exists.\n6. Fetch the exact page or section needed before answering.\n7. Cite retrieved official sources for links, quotes, and precise claims.\n\n## Migration rules\n\n- Keep upgrades behavior-preserving. Update active OpenAI model defaults, directly related prompts, and only the registries, routing, pricing, capability, or picker surfaces the user placed in scope.\n- Preserve multi-model cost, latency, and quality roles. Do not collapse a router or picker into one flagship model.\n- Leave historical docs, examples, eval baselines, fixtures, provider comparisons, intentionally pinned fallbacks, and ambiguous older usage unchanged unless explicitly requested.\n- Keep SDK, tooling, IDE, plugin, shell, auth, and provider-environment migrations out of a model-and-prompt upgrade unless explicitly requested.\n- If a safe change requires endpoint or schema rewiring, tool-handler changes, state changes, or another compatibility migration outside scope, report the exact blocker or ask for confirmation.\n\n## Validation\n\nAfter changes, run targeted tests for changed behavior and the most relevant type, lint, build, or smoke checks available. For model migrations, verify every active default surface in scope and exercise representative requests or evals. If validation cannot run, state why and name the next best check.\n\n## Rules\n\n- Treat live OpenAI documentation as the source of truth; never use bundled model guidance as a fallback.\n- Preserve explicit model targets.\n- Prefer concise summaries over long excerpts.\n- If sources conflict, state the difference. If evidence is missing, narrow the answer instead of guessing.\n",{"name":5,"description":7},"main","773bf911a0526a3f4bd395af6dd6de003917298c","skills\u002Fopenai-docs",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":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add openai\u002Fopenai-developers-for-cursor --skill openai-docs",{"tool":62,"command":63},"bunx","bunx skills add openai\u002Fopenai-developers-for-cursor --skill openai-docs",{"tool":65,"command":66},"pnpm","pnpm dlx skills add openai\u002Fopenai-developers-for-cursor --skill openai-docs","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fopenai\u002Fopenai-developers-for-cursor\u002Fblob\u002Fmain\u002Fskills\u002Fopenai-docs\u002FSKILL.md",true,[],[71,103,115,131,145],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":85,"publishedAt":43},"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",[77,80],{"categoryNo":78,"categoryName":79,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":81,"categoryName":82,"taxonomyType":83,"taxonomyTypeDesc":84},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[9,86,40,87,88,89,90,91,92,93,94,95,96,97,98,38,99,100,101,102],"openai platform api key","platform","as","work","guide","ui","input","cli","run","offline","forms","app","never","local","only","configure","ask",{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":111,"publishedAt":43},"01M6AC6XMX7SVT6EZNVKCVGR22","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.","https:\u002F\u002Fgithub.com\u002Fopenai\u002Fopenai-developers-for-cursor\u002Fblob\u002Fmain\u002Fskills\u002Fopenai-api-troubleshooting\u002FSKILL.md",[109,110],{"categoryNo":78,"categoryName":79,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":81,"categoryName":82,"taxonomyType":83,"taxonomyTypeDesc":84},[112,113,9,114,24],"openai api troubleshooting","openai api","setup",{"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":43},"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":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[123,124,125,27,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":43},"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":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[139,124,140,27,9,113,24,128,141,142,143,144],"build chatgpt app","code","sdk","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":43},"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,141,9,24,153,94],"agents sdk","workflow"]