CtrlK
BlogDocsLog inGet started
Tessl Logo

codex

Use when the user asks to run Codex CLI (codex exec, codex resume) or references OpenAI Codex for code analysis, refactoring, or automated editing. Uses GPT-5.2 by default for state-of-the-art software engineering.

88

4.00x
Quality

86%

Does it follow best practices?

Impact

88%

4.00x

Average score across 3 eval scenarios

SecuritybySnyk

Medium

Suggest reviewing before use

The canonical home for this skill is codex in jdrhyne/agent-skills

SKILL.md
Quality
Evals
Security

Quality

Content

86%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 highly actionable with executable commands and a clear workflow, well-organized into focused sections. Fixing the duplicate step numbering and adding an explicit validation feedback loop for destructive sandbox modes would push it higher.

Suggestions

Fix the duplicate step numbering in 'Running a Task' (two steps are both labeled '3'), which harms workflow clarity.

Add an explicit validate->fix->retry feedback loop for destructive/batch sandbox modes (workspace-write, danger-full-access) to satisfy the destructive-ops validation cap.

Trim minor padding such as 'state-of-the-art software engineering' to improve token efficiency.

DimensionReasoningScore

Conciseness

Mostly efficient tables and numbered commands, with minor trimmable padding ('state-of-the-art software engineering') and a duplicated step numbering (two step '3's); not quite lean enough for a 5.

4 / 5

Actionability

Provides fully executable, copy-paste-ready commands and a quick-reference table covering the common cases (read-only, workspace-write, danger-full-access, resume).

5 / 5

Workflow Clarity

Clear numbered sequence with checkpoints (non-zero exit handling, permission prompts for high-impact flags), but destructive modes lack an explicit validate->fix->retry feedback loop and the step numbering bug slightly harms clarity.

4 / 5

Progressive Disclosure

No bundle files exist and the single SKILL.md is well-organized into clear sections of appropriate length, satisfying the simple-skill exception for progressive disclosure.

5 / 5

Total

18

/

20

Passed

Description

87%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 strong: it pairs a concrete 'Use when...' trigger clause with named commands and a clear action list, cleanly answering both what and when. Minor room to broaden trigger synonyms and add more distinct actions.

DimensionReasoningScore

Specificity

Names concrete actions ('code analysis, refactoring, or automated editing' and running 'codex exec, codex resume') covering several specific operations; not quite comprehensive enough for a 5.

4 / 5

Completeness

Explicitly answers both what ('code analysis, refactoring, or automated editing') and when ('Use when the user asks to run Codex CLI...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural command-keyword triggers ('run Codex CLI (codex exec, codex resume)', 'references OpenAI Codex') users would say; a few broader synonyms are missing, so not a 5.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (OpenAI Codex CLI) with distinct command-name triggers, making overlap with other skills minimal.

5 / 5

Total

18

/

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
bap-jorkim/agent-skills-fork-feb-25
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.