OpenAI Developer Docs
v1.0.0Query 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.
⭐ 1· 2.1k·12 current·12 all-time
by@am-will
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description, SKILL.md, and the included script all implement the same capability: searching and fetching OpenAI developer docs via an MCP server. No unrelated services, credentials, or excessive capabilities are requested.
Instruction Scope
The runtime instructions are narrowly scoped to search/list/fetch docs via the provided CLI script. However, the script invokes curl and jq (and checks for them at runtime); the registry metadata listed no required binaries, which is a minor mismatch in the declared requirements.
Install Mechanism
There is no install specification (instruction-only skill with a shipped script). Nothing is downloaded or executed from unknown remote URLs during install.
Credentials
The skill does not require credentials and only exposes an optional MCP_URL environment override. That is reasonable, but setting MCP_URL to an untrusted endpoint would redirect all queries (and their contents) to that server — users should only use the official endpoint or a trusted proxy.
Persistence & Privilege
The skill does not request always:true, does not modify other skills, and does not persist credentials or alter system-wide settings. It runs only when invoked.
Assessment
This skill is coherent and appears to do what it says: it queries an OpenAI MCP docs endpoint and returns content. Before installing: (1) verify you trust the MCP endpoint (default: https://developers.openai.com/mcp); do not set MCP_URL to an untrusted server because your queries (which may include sensitive content) would be sent there; (2) ensure curl and jq are available on the agent host (the script will fail otherwise) — the registry metadata omitted those required binaries; (3) review the script to confirm you’re comfortable with it making outbound HTTP requests; and (4) if you need stricter controls, run the script in an environment with restricted network access or audit network logs to confirm it only contacts approved endpoints.Like a lobster shell, security has layers — review code before you run it.
latestvk977ys0e71p0w7j5jbkcb0argd7zdk17
License
MIT-0
Free to use, modify, and redistribute. No attribution required.