openai-docs-skill
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.
95
93%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong, well-crafted skill description that clearly identifies what the skill does (queries OpenAI docs via MCP server), when to use it (any task involving OpenAI APIs, SDKs, or related topics), and includes rich trigger terms covering the breadth of OpenAI's ecosystem. The only minor note is the use of second person 'you need' in the trigger clause, but the primary voice is third person, so the impact is minimal.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple concrete actions and domains: querying OpenAI docs via MCP server using CLI (curl/jq), and enumerates specific APIs (Responses, Chat Completions, Realtime), SDKs, ChatGPT Apps SDK, Codex, MCP integrations, endpoint schemas, parameters, limits, and migrations. | 3 / 3 |
Completeness | Clearly answers both 'what' (query OpenAI developer documentation via MCP server using CLI) and 'when' ('Use whenever a task involves the OpenAI API... and you need up-to-date official guidance'), with explicit trigger conditions. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'OpenAI API', 'Chat Completions', 'Realtime', 'OpenAI SDKs', 'ChatGPT', 'Codex', 'endpoint schemas', 'parameters', 'limits', 'migrations'. These are terms developers naturally use when seeking OpenAI documentation help. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — specifically targets OpenAI documentation querying via a specific MCP server, with clear domain boundaries (OpenAI API, SDKs, Codex). Unlikely to conflict with other skills unless there's another OpenAI docs skill. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted, concise skill that provides clear, actionable guidance for querying OpenAI docs via MCP. Its main weakness is the workflow section, which could benefit from error handling guidance (e.g., what to do when search returns irrelevant results or fetch fails). Overall it's efficient and practical.
Suggestions
Add brief error handling guidance to the workflow, e.g., 'If search returns no relevant results, try broader/narrower query terms' or 'If fetch returns an error, verify the URL format.'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It doesn't explain what OpenAI is, what MCP is, or how curl/jq work. Every section adds actionable information Claude wouldn't already know. | 3 / 3 |
Actionability | Provides concrete, copy-paste ready bash commands for searching and fetching docs. The script reference lists all subcommands with their exact syntax and parameters, making usage unambiguous. | 3 / 3 |
Workflow Clarity | The 3-step workflow (Discover → Read → Apply) is clear and sequenced, but lacks validation checkpoints. There's no guidance on what to do if search returns no results, if fetch fails, or how to verify the fetched content is current/relevant. | 2 / 3 |
Progressive Disclosure | For a skill under 50 lines, the content is well-organized with clear sections (Overview, Core rules, Quick start, Workflow, Script reference). The script reference is appropriately inline given its brevity, and no deeper nesting is needed. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- am-will/codex-skills
- Commit
633b7e0
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.