CtrlK
BlogDocsLog inGet started
Tessl Logo

openai-docs

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.

68

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Critical

Do not install without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

67%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, actionable skill body with concrete MCP tooling, a clear workflow, and explicit fallback/retry logic. The main weaknesses are mild redundancy and product-definition padding that hurt conciseness, plus the absence of a worked search/fetch example.

Suggestions

Remove or trim the 'OpenAI product snapshots' one-line definitions (concepts Claude already knows) and keep only the product names as trigger scoping.

Deduplicate the MCP-priority guidance so it appears once instead of in both the intro and 'Tooling notes'.

Add one concrete example showing a search query and a fetch_openai_doc call with its arguments to lift actionability toward fully copy-paste-ready.

DimensionReasoningScore

Conciseness

The body is mostly efficient, but the 'OpenAI product snapshots' section defines products Claude already knows (e.g. 'Codex: OpenAI's coding agent...') and the MCP-priority rule is restated across the intro and 'Tooling notes', so it could be tightened.

3 / 5

Actionability

Provides concrete executable tool names (mcp__openaiDeveloperDocs__search_openai_docs, fetch_openai_doc, list_openai_docs) and a copy-paste install command, but stops short of an example search query or fetch call with arguments, leaving a minor gap.

4 / 5

Workflow Clarity

A clear 5-step Workflow is present and the 'If MCP server is missing' flow includes explicit retry/restart feedback loops; the main workflow lacks an explicit checkpoint confirming search returned results before fetching, a minor validation gap.

4 / 5

Progressive Disclosure

Content is well-organized into clearly signaled self-contained sections with no need for external references, but the body sits around the 50-line simple-skill boundary and the product-snapshot list is the kind of content that could optionally live in a reference file, so it is just below the 5 anchor.

4 / 5

Total

15

/

20

Passed

Description

95%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, well-constructed description with an explicit 'Use when' trigger, comprehensive natural product keywords, and a clearly distinct OpenAI-docs niche. The only minor gap is that the skill's concrete actions reduce to a single retrieve-and-cite capability rather than a list of distinct operations.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions (provide cited official docs, prioritize OpenAI docs MCP tools, restrict fallback browsing to official domains) plus a broad product list, but the core capability is essentially a single retrieval-and-cite action rather than many distinct actions, so it sits just below the comprehensive 5 anchor.

4 / 5

Completeness

Explicitly answers both 'what' (up-to-date official documentation with citations via OpenAI docs MCP tools) and 'when' with a concrete 'Use when the user asks how to build with OpenAI products or APIs...' trigger plus examples.

5 / 5

Trigger Term Quality

Comprehensive coverage of natural terms users would actually say — 'Codex, Responses API, Chat Completions, Apps SDK, Agents SDK, Realtime, model capabilities or limits' — matching the breadth of the 5 anchor's example.

5 / 5

Distinctiveness Conflict Risk

Clear niche scoped narrowly to OpenAI developer documentation with product-specific triggers, giving minimal overlap risk with other skills.

5 / 5

Total

19

/

20

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
foryourhealth111-pixel/Vibe-Skills
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.