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.

86

2.67x
Quality

Does it follow best practices?

Impact

99%

2.67x

Average score across 3 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, well-sequenced skill body with executable commands and real monitoring checkpoints. The main weaknesses are mild verbosity in the reference/explanation portions and the lack of any progressive-disclosure split for a skill of this length.

Suggestions

Tighten the model and sandbox reference lists to bare flags without prose commentary to improve token efficiency.

Move the extended Examples section and the model/sandbox reference tables into a referenced file (e.g., reference/options.md) to introduce one-level-deep progressive disclosure for a skill of this length.

DimensionReasoningScore

Conciseness

The body is mostly efficient and actionable, but includes explanatory padding — e.g., 'gpt-5.2-codex - Default for Codex CLI, optimized for agentic coding (user's current config)' and rationale lines like 'streams indefinitely, wastes context' — that could be tightened, so it sits between lean and verbose.

2 / 3

Actionability

It provides concrete, executable commands throughout — 'git rev-parse --show-toplevel', 'codex exec --json -o ... - <<'CODEX_PROMPT'', 'wc -l < .../progress-*.jsonl' — with specific flag rules and copy-paste-ready blocks.

3 / 3

Workflow Clarity

A clearly sequenced process (Parse Arguments → Assess Complexity → Gather Context → Generate Prompt → Execute → Monitor → Return) with explicit checkpoints: 'First: check if summary file exists (finished?)', then 'wc -l' to confirm activity, plus a git-repo guard before running.

3 / 3

Progressive Disclosure

Content is well organized into clear sections, but as a ~270-line skill with no bundle files or external references, material such as the model/sandbox reference lists and examples is all inline rather than split out, which is appropriate for a single-file skill but leaves no layered navigation.

2 / 3

Total

10

/

12

Passed

Description

85%

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 clearly states both the capability and the trigger, with concrete actions and a distinct niche. Its main weakness is the somewhat abstract trigger framing rather than natural user phrasings.

Suggestions

Rewrite the 'Use when' clause around concrete user phrasings (e.g., 'Use when the user asks to implement a feature, fix a bug, review changes, or investigate an issue') to improve trigger-term quality.

Consider dropping or tightening the trailing 'Codex has full codebase access and can make changes' since it slightly pads the description without adding trigger value.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'implement, fix, investigate, or review code' — and a concrete mechanism ('Hand off a task to Codex CLI for autonomous execution'), matching the highest anchor.

3 / 3

Completeness

It explicitly answers both what ('Hand off a task to Codex CLI for autonomous execution') and when ('Use when a task would benefit from a capable subagent...'), with an explicit 'Use when' trigger clause.

3 / 3

Trigger Term Quality

It includes relevant natural terms ('implement, fix, investigate, or review code'), but the trigger is framed abstractly ('a task would benefit from a capable subagent') rather than as user-facing phrasings like 'fix a bug' or 'review my changes', missing common variations.

2 / 3

Distinctiveness Conflict Risk

Naming a specific tool ('Codex CLI') and a clear delegation niche ('capable subagent') gives it distinct triggers unlikely to collide with other skills.

3 / 3

Total

11

/

12

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.