CtrlK
BlogDocsLog inGet started
Tessl Logo

codex

Delegate coding work to the OpenAI Codex CLI for repository changes, reviews, and focused fixes.

64

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/agents/codex/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

91%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 content is lean, highly actionable, and well-structured into clear sections with executable examples covering the main use cases. The only minor gap is that validation/verification steps for destructive and batch operations (worktrees, --full-auto writes) are described in prose rather than as explicit validate-then-proceed checkpoints.

DimensionReasoningScore

Conciseness

The body is lean throughout, with no padding or explanation of concepts Claude already knows; sections like "Prerequisites", "When to Use", and code blocks each earn their tokens with concrete, scannable guidance.

5 / 5

Actionability

Commands are copy-paste ready and cover common cases — "codex exec "..."", worktree setup, PR checkout via gh — with explicit flags like --full-auto and pty=true, matching the fully executable anchor.

5 / 5

Workflow Clarity

Sequences are clear (worktree add -> cd -> exec -> inspect -> remove) with implicit checkpoints like "inspect the diff, run the expected checks", but validation steps are phrased as prose rather than explicit validate-then-proceed feedback loops, leaving minor gaps.

4 / 5

Progressive Disclosure

At roughly 100 lines with no external bundle files, the skill is well-organized into clearly headed sections that fit a single overview file; per the simple-skills note, well-organized content with no need for external references scores 5.

5 / 5

Total

19

/

20

Passed

Description

61%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 specific and distinctive, naming the Codex CLI and concrete repository actions, but it omits any explicit "Use when..." trigger guidance, which limits completeness. Adding a trigger clause would lift it toward the top anchors.

Suggestions

Append an explicit trigger clause, e.g. "Use when the user wants an autonomous coding pass in a git repository or asks for a second coding agent to review, fix, or investigate code."

Add a couple of natural synonyms users say ("refactor", "bug fix", "PR review") to broaden trigger coverage.

Keep the third-person voice and concise phrasing; just extend completeness rather than padding.

DimensionReasoningScore

Specificity

Quotes "Delegate coding work" and "repository changes, reviews, and focused fixes" name the domain plus a few concrete actions, but coverage stays generic without naming specific capability types beyond the three listed.

3 / 5

Completeness

The "what" is clear ("Delegate coding work to the OpenAI Codex CLI") but there is no explicit "Use when..." trigger clause, which per the guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

Natural terms like "coding work", "repository changes", "reviews", and "focused fixes" map to phrasing a user would say, though common synonyms like "refactor", "bug fix", or "PR review" are absent from the description itself.

4 / 5

Distinctiveness Conflict Risk

Scoping to "the OpenAI Codex CLI" and "repository changes, reviews, and focused fixes" carves a clear niche with only minor overlap risk against general coding or git skills.

4 / 5

Total

14

/

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

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository
Open-Curiosity/gini-agent
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.