domains / families / agent-tooling / openai-docs
Query the OpenAI developer documentation via the OpenAI Docs MCP server using CLI (curl/jq). Use whenever a task involves the OpenAI API (Responses, Chat Completions, Realtime, etc.), OpenAI SDKs, ChatGPT Apps SDK, Codex, MCP integrations, endpoint schemas, parameters, limits, or migrations and you need up-to-date official guidance. Use when the user asks how to build with OpenAI products or APIs and needs up-to-date official documentation with citations (for example: Codex, Responses API, Chat Completions, Apps SDK, Agents SDK, Realtime, model capabilities or limits); prioritize OpenAI docs MCP tools and restrict any fallback browsing to official OpenAI domains.
The three copies overlap on the core task (querying OpenAI developer docs via the developers.openai.com MCP server and citing official sources), but each has material steps the others lack. The openai/skills copy adds Codex self-knowledge routing, a local manual-fetch helper, model-selection/migration guidance, and an OpenAPI spec tool. The Vibe-Skills copy adds an MCP install/restart recovery flow and explicit quality rules. The am-will copy uses a different access mechanism (a curl/jq CLI wrapper script) and exposes subcommands like endpoints/openapi. Crowning one copy would hide real alternatives, so the combined instruction preserves the shared workflow and lists the divergent access and recovery paths under Conflicts.