CtrlK
BlogDocsLog inGet started
Tessl Logo

openai-docs

Use when the user asks how to build with OpenAI products or APIs, asks about Codex itself or choosing Codex surfaces, needs up-to-date official documentation with citations, help choosing the latest model for a use case, or model upgrade and prompt-upgrade guidance; use OpenAI docs MCP tools for non-Codex docs questions, use the Codex manual helper first for broad Codex self-knowledge, and restrict fallback browsing to official OpenAI domains.

75

Quality

92%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

85%

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

The body is highly actionable and well-structured with explicit numbered workflows, validation checkpoints, error-recovery feedback loops, and a clean one-level-deep reference map pointing to real bundle files. Its weakness is conciseness: dense conditional prose and restated model-selection guidance across several sections could be consolidated.

Suggestions

Consolidate the model-selection guidance so it lives in one place (e.g., Workflow step 3) rather than being restated across Source Priority, Workflow, and Reference map.

Tighten the Codex source route by collapsing repetitive conditional clauses ('If the manual...', 'If the helper is skipped...', 'Use the narrowest official next source only when...') into a compact decision table.

DimensionReasoningScore

Conciseness

The body is procedural and avoids explaining basic concepts Claude knows, but it is dense and repetitive — model-selection guidance is restated across 'Source Priority', 'Workflow' step 3, and 'Reference map', and the Codex source route is padded with conditional hedging that could be tightened.

2 / 3

Actionability

Provides concrete, executable guidance for an instruction skill: exact MCP tool identifiers, `node <skill-dir>/scripts/fetch-codex-manual.mjs`, `node scripts/resolve-latest-model-info.js`, `codex mcp add openaiDeveloperDocs --url ...`, and specific URLs/anchors to fetch.

3 / 3

Workflow Clarity

Multiple clearly sequenced numbered workflows (Codex Source Route 1-4, Workflow 1-8, MCP-missing recovery 1-5) with explicit validation checkpoints (manual freshness checks) and feedback loops (helper failure → next source; install fail → escalate → ask user → restart → re-run).

3 / 3

Progressive Disclosure

A dedicated 'Reference map' clearly signals one-level-deep references (references/latest-model.md, upgrade-guide.md, prompting-guide.md, scripts/*) that all resolve to real bundle files, with detailed model/upgrade/prompting content appropriately split out of the body.

3 / 3

Total

11

/

12

Passed

Description

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.

The description is strong across all four dimensions: it states concrete capabilities, natural trigger terms, explicit 'when' guidance, and a distinct OpenAI/Codex niche. Its main weakness is verbosity — a 60+ word run-on sentence that folds internal routing mechanics ('use OpenAI docs MCP tools...', 'use the Codex manual helper first...') into what should be a concise trigger description.

Suggestions

Tighten the description by moving internal routing mechanics (MCP-tool vs. manual-helper vs. web-fallback ordering) into the body and keeping the description to concrete triggers and a 'Use when...' clause.

Split the single run-on sentence into a short capability statement followed by a distinct 'Use when...' trigger clause for readability.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: 'how to build with OpenAI products or APIs', 'asks about Codex itself', 'needs up-to-date official documentation with citations', 'choosing the latest model', 'model upgrade and prompt-upgrade guidance' — concrete capabilities, not abstract language.

3 / 3

Completeness

Explicitly states both what it does (OpenAI/Codex docs, model selection, upgrades, prompt upgrades) and when to use it via an explicit 'Use when...' clause with multiple concrete triggers.

3 / 3

Trigger Term Quality

Covers natural user phrasing such as 'how to build with OpenAI products or APIs', 'Codex itself', 'latest model', 'model upgrade', and 'prompt-upgrade guidance' that a user would plausibly say when needing this skill.

3 / 3

Distinctiveness Conflict Risk

Clear OpenAI/Codex niche with distinct triggers and boundary language ('restrict fallback browsing to official OpenAI domains') that sharply limits overlap with unrelated skills.

3 / 3

Total

12

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
openai/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.