OpenAI Docs

Provide authoritative, current guidance from OpenAI developer docs using an OpenAI developer docs MCP integration when the current host supports it. Always prioritize that docs integration over general web search for OpenAI-related questions. This skill may also load targeted files from references/ for model-selection and GPT-5.4-specific requests, but current OpenAI docs remain authoritative. Only if the docs integration is unavailable or returns no meaningful results should you fall back to official web docs.

Quick start

• Use the current host's OpenAI docs search capability to find the most relevant doc pages.
• Use the current host's OpenAI docs fetch capability to pull exact sections and quote or paraphrase accurately.
• Use the current host's OpenAI docs listing capability only when you need to browse or discover pages without a clear query.
• Load only the relevant file from references/ when the question is about model selection or a GPT-5.4 upgrade.

OpenAI product snapshots

1. Apps SDK: Build ChatGPT apps by providing a web component UI and an MCP server that exposes your app's tools to ChatGPT.
2. Responses API: A unified endpoint designed for stateful, multimodal, tool-using interactions in agentic workflows.
3. Chat Completions API: Generate a model response from a list of messages comprising a conversation.
4. Codex: OpenAI's coding agent for software development that can write, understand, review, and debug code.
5. gpt-oss: Open-weight OpenAI reasoning models (gpt-oss-120b and gpt-oss-20b) released under the Apache 2.0 license.
6. Realtime API: Build low-latency, multimodal experiences including natural speech-to-speech conversations.
7. Agents SDK: A toolkit for building agentic apps where a model can use tools and context, hand off to other agents, stream partial results, and keep a full trace.

If the docs integration is missing

If no OpenAI docs MCP integration or equivalent host connector is available:

1. Check whether the current host supports MCP or official docs connectors.
2. If it does, connect an OpenAI developer docs MCP server or equivalent docs source for that host.
3. If the current host cannot connect an MCP server directly, use official OpenAI web docs as the fallback source.
4. Re-run the doc search and fetch flow once the docs source is available.

Workflow

1. Clarify the product scope and whether the request is general docs lookup, model selection, a GPT-5.4 upgrade, or a GPT-5.4 prompt upgrade.
2. If it is a model-selection request, load references/latest-model.md.
3. If it is an explicit GPT-5.4 upgrade request, load references/upgrading-to-gpt-5p4.md.
4. If the upgrade may require prompt changes, or the workflow is research-heavy, tool-heavy, coding-oriented, multi-agent, or long-running, also load references/gpt-5p4-prompting-guide.md.
5. Search docs with a precise query.
6. Fetch the best page and the exact section needed (use anchor when possible).
7. For GPT-5.4 upgrade reviews, always make the per-usage-site output explicit: target model, starting reasoning recommendation, phase assessment when relevant, prompt blocks, and compatibility status.
8. Answer with concise guidance and cite the doc source, using the reference files only as helper context.

Reference map

Read only what you need:

• references/latest-model.md -> model-selection and "best/latest/current model" questions; verify every recommendation against current OpenAI docs before answering.
• references/upgrading-to-gpt-5p4.md -> only for explicit GPT-5.4 upgrade and upgrade-planning requests; verify the checklist and compatibility guidance against current OpenAI docs before answering.
• references/gpt-5p4-prompting-guide.md -> prompt rewrites and prompt-behavior upgrades for GPT-5.4; verify prompting guidance against current OpenAI docs before answering.

Quality rules

• Treat OpenAI docs as the source of truth; avoid speculation.
• Keep quotes short and within policy limits; prefer paraphrase with citations.
• If multiple pages differ, call out the difference and cite both.
• Reference files are convenience guides only; for volatile guidance such as recommended models, upgrade instructions, or prompting advice, current OpenAI docs always win.
• If docs do not cover the user’s need, say so and offer next steps.

Tooling notes

• Always use an OpenAI docs MCP integration or equivalent host docs connector before any web search for OpenAI-related questions.
• If the docs integration is available but returns no meaningful results, then use web search as a fallback.
• When falling back to web search, restrict to official OpenAI domains (developers.openai.com, platform.openai.com) and cite sources.