CtrlK
BlogDocsLog inGet started
Tessl Logo

openai-docs

Use for Codex models/pricing, scheduled tasks, skills, settings, setup, troubleshooting, customization, automations, and self-knowledge—including 'you,' 'your,' 'this app,' or 'this coding agent' when they refer to Codex—and for OpenAI APIs/products and ChatGPT Work. Also use for model choice/migration, prompting, SDKs, Responses, Realtime, agents, evals, and Chat/Work/Codex comparisons. Do not use for generic app/software tasks that merely mention Codex.

61

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./codex-rs/skills/src/assets/samples/openai-docs/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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.

The body is a well-structured, actionable routing guide with excellent progressive disclosure and a clear source-order workflow; its main weakness is redundant restatement of the same fetch/source-order rule, which inflates length without adding guidance.

Suggestions

State the official-source-first rule once in a short numbered sequence and remove its restatements in the 'First substantive action' paragraph and the boundaries section.

Break the long 'First substantive action' run-on into 2-3 short steps so the workflow checkpoints are explicit instead of buried in prose.

DimensionReasoningScore

Conciseness

The body is mostly efficient instruction with no concept-padding, but restates the source-order rule multiple times ('actually open or fetch', 'Use the actual fetched page, not a search snippet or an unopened link', and again in the boundaries section) and the 'First substantive action' paragraph is a dense run-on that could be trimmed.

3 / 5

Actionability

Concrete, executable guidance throughout — exact allowed domains ('developers.openai.com', 'platform.openai.com', 'learn.chatgpt.com'), exact reference paths per route, and a concrete pre-action ('use openai-platform-api-key first'); minor gaps come from the conditional routing being complex to apply in edge cases.

4 / 5

Workflow Clarity

A clear source-order sequence (search → fetch page → cite) with a fallback loop ('If one official search or page does not establish the answer, search another appropriate official domain') and an ordered route-selection list; checkpoints are present but somewhat implicit inside prose rather than a clean numbered workflow.

4 / 5

Progressive Disclosure

A concise overview routes to nine real, one-level-deep reference files via clear markdown links, each tied to a specific scenario, with no inlined bulk content and no nested references — well-signaled and easy to navigate.

5 / 5

Total

16

/

20

Passed

Description

73%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.

The description is a thorough, well-bounded trigger catalogue with excellent 'when' guidance and strong distinctiveness, but it leans on the generic 'Use for' action rather than stating concrete capabilities, leaving the 'what' somewhat implicit.

Suggestions

Lead with one concrete action clause (e.g., 'Provide current, cited OpenAI product, API, model, and Codex guidance') before the 'Use for...' triggers so the 'what' is explicit, not just the 'when'.

Tighten the long mid-sentence enumeration into scannable trigger groups so natural keywords stand out rather than being buried in a run-on clause.

DimensionReasoningScore

Specificity

Names many specific OpenAI/Codex domains ('Codex models/pricing, scheduled tasks, skills, settings, setup, troubleshooting, customization, automations') but the action verb is the generic 'Use for' rather than concrete discrete actions, so it sits at 'names domain + clear general action' rather than a list of specific actions.

3 / 5

Completeness

An exceptionally explicit 'when' ('Use for...', 'Also use for...', 'Do not use for generic app/software tasks that merely mention Codex') is present, but the 'what' is implied rather than stated with a concrete action verb, so it has both with the 'what' recoverable but not as crisp as the anchor 5 example.

4 / 5

Trigger Term Quality

Strong, natural keyword coverage including synonyms and self-reference phrasings ("'you,' 'your,' 'this app,' or 'this coding agent'"), 'model choice/migration, prompting, SDKs, Responses, Realtime, agents, evals' — comprehensive but a few natural user phrasings are still implicit.

4 / 5

Distinctiveness Conflict Risk

A clear OpenAI/Codex-docs niche with an explicit anti-conflict clause ('Do not use for generic app/software tasks that merely mention Codex') and 'you'/'this app' means Codex disambiguation, giving minimal trigger-conflict risk.

5 / 5

Total

16

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

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