CtrlK
BlogDocsLog inGet started
Tessl Logo

codex

Hand off a task to Codex CLI for autonomous execution. Use when a task would benefit from a capable subagent to implement, fix, investigate, or review code. Codex has full codebase access and can make changes.

83

2.67x
Quality

75%

Does it follow best practices?

Impact

99%

2.67x

Average score across 3 eval scenarios

SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./data/skills-md/0xbigboss/claude-code/codex/SKILL.md
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 concrete, well-sequenced operational skill with real executable commands and clear monitoring guidance. It is held back primarily by verbosity (repeated output-file descriptions, self-evident model/sandbox blurbs) and validation that is delegated rather than independently verified.

Suggestions

Describe the progress-*.jsonl and summary-*.txt output files once in 'Session Info' and reference them by name later, instead of re-describing them in 'Monitoring Execution' and 'Return Result'.

Trim self-evident glosses on sandbox modes and models (e.g. 'read-only - No file modifications allowed', 'Flagship model, best for complex professional tasks') to just the values Claude needs to select them.

Add an independent verification step after Codex completes (e.g. re-run tests or inspect `git diff`) so validation is not solely self-reported by Codex's summary.

DimensionReasoningScore

Conciseness

Mostly efficient operational content, but it pads self-evident items (sandbox modes like 'read-only - No file modifications allowed', model blurbs like 'Flagship model, best for complex professional tasks') and describes the progress/summary output files in three separate sections.

3 / 5

Actionability

Provides concrete executable commands (git rev-parse, mkdir -p, codex exec --json, wc -l, tail -n 3) and an explicit flag-rules section, but unfilled placeholders ({timestamp}, {required_flags}, {generated_prompt}) keep it from copy-paste-ready level 5.

4 / 5

Workflow Clarity

Clear sequenced workflow (Parse → Assess → Gather → Generate → Execute → Return) with explicit monitoring checkpoints, but validation is delegated to Codex and self-reported rather than independently verified by the calling skill.

4 / 5

Progressive Disclosure

Well-organized single file with clear section headers and no nested references, but at ~271 lines the inlined model/sandbox lists could arguably live in a separate reference, keeping it below the well-split level 5.

4 / 5

Total

15

/

20

Passed

Description

83%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 cleanly states the skill's purpose and gives an explicit, concrete 'Use when' trigger covering multiple natural verbs. Its main limitation is that the listed actions are general coding verbs rather than highly specific operations.

DimensionReasoningScore

Specificity

Lists several concrete actions ('implement, fix, investigate, or review code', 'can make changes') but these are generic coding verbs rather than the specific operations a 5 requires.

4 / 5

Completeness

Explicitly answers both 'what' ('Hand off a task to Codex CLI for autonomous execution', 'Codex has full codebase access and can make changes') and 'when' via a concrete 'Use when a task would benefit from a capable subagent to...' trigger clause.

5 / 5

Trigger Term Quality

Good coverage of natural terms users would say ('implement', 'fix', 'investigate', 'review code'), but lacks synonyms or the kind of extension-specific variations a 5 demands.

4 / 5

Distinctiveness Conflict Risk

Has a clear Codex-CLI/subagent niche with distinct triggers, but could overlap with other generic delegation or subagent skills, so it is not at minimal-conflict level 5.

4 / 5

Total

17

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository
NeverSight/skills_feed
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.