Openai Docs
Wire your coding agent to official OpenAI Developer documentation so API and platform answers stay accurate and cited instead of guessed from training data.
Overview
OpenAI Docs is an agent skill most often used in Build (also Validate, Ship) that looks up the official OpenAI Developer documentation via MCP and returns concise, cited guidance.
Install
npx skills add https://github.com/boshu2/agentops --skill openai-docsWhat is this skill?
- Connects via the OpenAI Developer Docs MCP server over streamable HTTP at developers.openai.com/mcp
- Default prompt steers agents to look up official docs and reply with concise, cited guidance
- Packaged as an AgentOps interface skill with display name, icons, and MCP dependency metadata
- Reduces hallucinated parameters, deprecations, and endpoint behavior when building on OpenAI
- Fits Claude Code, Cursor, and other MCP-capable agents without maintaining a local doc mirror
Adoption & trust: 738 installs on skills.sh; 384 GitHub stars; 1/3 security scanners passed (skills.sh audits).
What problem does it solve?
You are coding against OpenAI’s platform but the agent’s answers might be stale, incomplete, or wrong without a hook to the current developer docs.
Who is it for?
Solo builders adding or debugging OpenAI API integrations who already run MCP-capable agents and want doc-backed answers in the same thread.
Skip if: Teams that need offline-only workflows, non-OpenAI providers only, or a substitute for reading security and compliance requirements before production deploys.
When should I use this skill?
You need official OpenAI Developer documentation cited for the task at hand—models, APIs, tools, or platform behavior.
What do I get? / Deliverables
Your agent queries the official OpenAI Developer Docs MCP server and answers with guidance grounded in citable documentation instead of improvisation.
- Concise answers with pointers to official OpenAI developer documentation
- Cited parameter and behavior notes aligned to the queried API or feature
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Most installs happen while wiring OpenAI APIs, tools, and agents during implementation. The skill is an MCP-backed docs bridge—classic third-party/API integration work on the build shelf.
Where it fits
Compare Chat Completions vs Responses API options in official docs before committing to an architecture.
Confirm rate limits, auth headers, and tool schemas while implementing your first OpenAI-backed feature.
Double-check documented breaking changes and error codes before tagging a release that depends on a new API surface.
Look up current retry and idempotency guidance after production errors spike on an OpenAI endpoint.
How it compares
Use as a live documentation MCP bridge, not as a general web-search skill or a local mirror of third-party API docs.
Common Questions / FAQ
Who is openai-docs for?
Indie developers and small teams building on OpenAI—chat apps, agents, batch jobs, or SaaS backends—who want the coding agent to ground answers in developers.openai.com rather than memory.
When should I use openai-docs?
During Validate when scoping which OpenAI APIs fit your product; during Build when wiring endpoints, tools, and auth; during Ship when confirming behavior before release; during Operate when checking docs after errors or platform updates.
Is openai-docs safe to install?
It depends on your agent host and MCP trust model because the skill calls a remote documentation server over the network. Review the Security Audits panel on this Prism page and your org’s MCP allowlist before enabling it in production repos.
SKILL.md
READMESKILL.md - Openai Docs
interface: display_name: "OpenAI Docs" short_description: "Reference the official OpenAI Developer docs" icon_small: "./assets/openai-small.svg" icon_large: "./assets/openai.png" default_prompt: "Look up official OpenAI docs for this task and answer with concise, cited guidance." dependencies: tools: - type: "mcp" value: "openaiDeveloperDocs" description: "OpenAI Developer Docs MCP server" transport: "streamable_http" url: "https://developers.openai.com/mcp" <svg xmlns="http://www.w3.org/2000/svg" width="14" height="14" fill="currentColor" viewBox="0 0 14 14"> <path d="M10.931 3.34a.112.112 0 0 0-.069-.104l-.038-.007c-1.537.05-2.45.318-3.714 1.002v6.683c.48-.248.936-.44 1.414-.58.695-.203 1.417-.292 2.303-.305l.038-.008a.113.113 0 0 0 .066-.104V3.341ZM2.363 9.919c0 .064.051.11.105.111l.33.008c1.162.046 2.042.243 2.975.662-.403-.585-1.008-1.075-1.654-1.292a.991.991 0 0 1-.674-.941v-5.14a6.36 6.36 0 0 0-.59-.076l-.37-.02a.115.115 0 0 0-.122.111v6.577Zm9.455-.001a.998.998 0 0 1-.877.992l-.101.007c-.832.012-1.47.095-2.066.27-.599.174-1.176.448-1.883.863a.444.444 0 0 1-.449 0c-1.299-.763-2.229-1.07-3.689-1.125l-.299-.008a.997.997 0 0 1-.977-.998V3.342c0-.573.478-1.017 1.038-.999l.417.023c.188.015.35.037.513.062v-.754c0-.708.749-1.244 1.429-.903.984.492 1.836 1.449 2.15 2.505 1.216-.617 2.222-.884 3.771-.934l.105.003a.998.998 0 0 1 .918.996v6.576ZM4.332 8.466c0 .049.03.087.07.1l.24.091a4.319 4.319 0 0 1 1.581 1.176V3.721c-.164-.803-.799-1.617-1.584-2.07l-.162-.088c-.025-.012-.054-.013-.088.009a.12.12 0 0 0-.057.102v6.792Z"/> </svg> Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in