CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

codex-cli

Integrate OpenAI Codex CLI into Claude Code for AI collaboration, code generation, and automated development. Use when working with OpenAI models (GPT-5.2, GPT-5.1-Codex-Max, o3, o4-mini), code refactoring, git workflows, or needing full automation with permission bypass.

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 ./.claude/skills/codex-cli/SKILL.md

The canonical home for this skill is codex-cli in fernandezbaptiste/Skrillz

SKILL.md
Quality
Evals
Security

Quality

Content

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

Highly actionable content with executable commands and some well-structured workflows, including a real error-recovery loop. It is undermined by severe verbosity from duplicated examples and scattered version-dated material, a monolithic structure with zero progressive disclosure into bundle files, and batch destructive workflows that lack validation checkpoints.

Suggestions

Split reference material into bundle files — e.g. references/models.md (the model catalog with pricing), references/config.md (config.toml profiles and environment variables), and references/ci-cd.md — keeping SKILL.md as a concise overview with clearly signaled one-level-deep links, and remove the 'Related Skills' section or point it at files that actually exist.

Deduplicate examples: state the bypass/full-auto/sandbox flags once in an options section and reference them thereafter instead of repeating '--dangerously-bypass-approvals-and-sandbox' in ~20 examples; consolidate the three overlapping model-selection sections into one.

Consolidate time-sensitive details (GPT-5.2 release date, pricing, knowledge cutoffs) into a single clearly-labeled versions section, and add explicit validation checkpoints (e.g. run tests and review diffs before committing) to the batch destructive workflows that currently run unattended under bypass mode.

DimensionReasoningScore

Conciseness

The same flags and commands repeat across sections ('--dangerously-bypass-approvals-and-sandbox' appears verbatim in roughly 20 examples) and model-selection guidance is duplicated across three sections. Time-sensitive material ('December 2025', GPT-5.2 pricing, knowledge cutoff dates) is scattered throughout instead of quarantined in a versions/deprecated section, which the rubric explicitly penalizes. It is command-dense rather than re-teaching known concepts, keeping it above anchor 1 but firmly at anchor 2.

2 / 5

Actionability

Nearly everything is copy-paste executable: install/auth commands, full bash workflow functions (e.g. 'refactor_module' with git stash backup and restore on failure), a complete GitHub Actions YAML, and config.toml profile examples. Specific examples cover the common cases, matching anchor 5.

5 / 5

Workflow Clarity

Sequences are clearly laid out (Think-Act-Observe loop, 6-step task decomposition) and the refactoring workflow has a genuine feedback loop ('if [ $? -eq 0 ] ... else git stash pop'). However, many destructive/batch operations ('Convert all .js files to TypeScript', 'Run tests and auto-fix all failures', 'Achieve 100% coverage') run under bypass mode with no validation checkpoint, which caps this dimension at 3 per the rubric's batch-operations guideline.

3 / 5

Progressive Disclosure

The body is a 687-line monolith with no bundle files at all (no references/, scripts/, or assets/ exist), and material that clearly belongs in separate files — a ~100-line model catalog, ~80-line config reference, CI/CD pipeline example, and troubleshooting — is fully inlined. The 'Related Skills' section points to skills ('codex-auth', 'codex-git', etc.) that are not present. Section headers provide some structure, but the scale of inlining matches anchor 2 better than anchor 3.

2 / 5

Total

12

/

20

Passed

Description

78%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 description that explicitly states both what the skill does and when to use it, with good natural trigger terms including specific model names. Its main weaknesses are mild fluff ('AI collaboration') and generic trigger terms that overlap with general coding skills.

DimensionReasoningScore

Specificity

Concrete actions include 'Integrate OpenAI Codex CLI into Claude Code', 'code generation', and 'automated development', but 'AI collaboration' is fluffy and the action list is thinner and more abstract than the anchor-4 example's set of concrete operations. It names the domain plus 1-2 concrete actions rather than listing several specific ones, so it fits anchor 3, not 4.

3 / 5

Completeness

Explicitly answers both: what ('Integrate OpenAI Codex CLI into Claude Code for AI collaboration, code generation, and automated development') and when with concrete trigger phrases ('Use when working with OpenAI models (GPT-5.2, GPT-5.1-Codex-Max, o3, o4-mini), code refactoring, git workflows, or needing full automation with permission bypass'), matching the anchor-5 example structure. Voice is third-person imperative throughout.

5 / 5

Trigger Term Quality

Good natural keyword coverage: 'OpenAI models', specific model names ('GPT-5.2', 'GPT-5.1-Codex-Max', 'o3', 'o4-mini'), 'code refactoring', 'git workflows', 'permission bypass', plus 'Codex CLI' in the what-clause. A few natural phrasings (e.g. 'GPT', 'delegate to Codex') are missing, so it fits anchor 4 rather than the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

The Codex CLI/OpenAI model niche is distinct with dedicated triggers, but generic terms 'code refactoring' and 'git workflows' overlap with general-purpose coding skills, creating minor conflict risk. This is 'mostly distinct; minor overlap risk' (anchor 4) rather than the minimal-conflict anchor 5.

4 / 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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (690 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository

fernandezbaptiste/Skrillz

Path

.claude/skills/codex-cli/SKILL.md

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.