OpenAI Official Docs Assistant
Provides current, official-source guidance for OpenAI products, APIs, Codex, and model migrations.
The skill restricts retrieval to the official OpenAI Docs MCP and official-domain fallback, and describes an API-key gate plus read-only retrieval boundaries. Deductions apply because MCP data flows, sensitive-credential handling, user confirmation, rollback, and network-dependency risks are not fully specified.
Routing rules, fallbacks, cache validation, timeouts, and error handling are detailed, and the script implements hash verification and atomic writes. Static review cannot execute key paths; MCP availability, Windows/proxy behavior, and remote-response compatibility are not demonstrated by tests, so the score remains below the static ceiling.
The audience and core scenarios are reasonably clear: OpenAI documentation, Codex self-knowledge, model selection, and migration guidance, with some non-fit boundaries. Deductions apply because triggering is complex, Chinese-language output is not specified, and core functionality depends on the developers.openai.com MCP and official network access, which may be difficult from mainland China.
The skill has clear structure, dependency declaration, references, fallback rules, and Apache-2.0 licensing, with substantial progressive disclosure. Deductions apply for the absence of an independent version, changelog, named maintenance owner, and explicit update process; the bundled references also acknowledge drift risk.
For current OpenAI documentation, Codex self-knowledge, and model-migration tasks, the routing and guidance are directly useful and include compatibility and validation checklists. No representative outputs or execution evidence are included, and remote-tool failure may require manual handling, so this is limited to the static-review effectiveness ceiling.
The helper provides HTTP hash checks, cache status, and auditable local manual paths, while tool names and source URLs are specific. Deductions apply because there is no committed key-path test suite, CI execution evidence, or independent corroboration; much of the behavior depends on runtime MCP and network conditions.
- Core retrieval depends on the OpenAI Docs MCP and developers.openai.com; restricted mainland-China connectivity or an uninstalled MCP server may make key functionality unavailable.
- The bundled model and prompting references explicitly may drift; current documentation must be checked before presenting current recommendations.
- The script, MCP calls, and migration workflow were not executed in this static review; documented procedures should not be treated as tested behavior.
- The helper writes a temporary cache and accesses remote services; deployment-specific review is still needed for data flow, proxy configuration, and cached content.
What it does & when to use it
This Agent Skill from the openai/codex repository handles questions about OpenAI products and APIs. It prioritizes the OpenAI Developer Docs MCP and uses a Codex manual helper first for broad Codex questions. It also owns model selection, API model migration, and prompt-upgrade guidance, with fallback web searches restricted to official OpenAI domains. The repository is licensed under Apache-2.0, but the source does not document a standalone installation process for this Skill.
Classifies requests and selects the Codex manual helper, OpenAI Developer Docs MCP, or official-domain web search; searches and fetches relevant official documentation; uses an OpenAPI specification tool for API reference, schema, parameter, or required-field questions when available; runs a model resolver to obtain current model, migration-guide, and prompting-guide URLs; and may read or write temporary cache files before producing cited guidance.
- A developer needs to verify how to call an OpenAI API or configure API parameters.
- A Codex user needs guidance on Codex configuration, customization, skills, plugins, MCP, or other product behavior.
- A team is selecting a current model or planning an API model migration.
- An engineer needs prompting guidance for a named GPT-5-family model.
- A reader wants an OpenAI documentation answer supported by official citations.
Pros & cons
- Explicitly prioritizes official OpenAI documentation and the Codex manual.
- Covers API documentation, Codex self-knowledge, model selection, model migration, and prompt upgrades.
- Can verify API references and OpenAPI specifications when the relevant tool is available.
- Restricts web fallback to official OpenAI domains.
- Depends on the OpenAI Developer Docs MCP, the Codex manual helper, or official network access.
- The model-resolution workflow requires Node.js 18 or newer.
- Temporary caching requires filesystem access.
- No standalone installation procedure, test suite, or cross-client validation evidence is provided.
How to install
The source only documents installation for the overall Codex CLI collection: on macOS or Linux run curl -fsSL https://chatgpt.com/codex/install.sh | sh; on Windows run powershell -ExecutionPolicy ByPass -c "irm https://chatgpt.com/codex/install.ps1 | iex"; or use npm install -g @openai/codex or brew install --cask codex. It does not document how to install this Skill independently into another client.
How to use
In an installed Codex environment, submit a focused request such as: “Using current official OpenAI documentation, explain how the Responses API supports a multimodal tool-using workflow and provide citations.” For Codex questions, ask directly about Codex configuration, skills, or MCP. The source does not specify an independent-client enablement command or complete trigger syntax.