CtrlK
BlogDocsLog inGet started
Tessl Logo

codex-review

Professional code review with auto CHANGELOG generation, integrated with Codex AI

46

Quality

48%

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 ./.agent/skills/codex-review/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

47%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 well-organized and token-efficient but thin on executable guidance: beyond the install command, the workflow steps and examples are vague or offloaded to an external repo with no concrete review or CHANGELOG-generation procedure. Validation checkpoints are entirely absent.

Suggestions

Add concrete, copy-paste-ready steps for the actual review and CHANGELOG generation workflow (e.g. exact Codex CLI invocation, diff command, CHANGELOG entry format) instead of 'Use /codex-review or natural language triggers'.

Include the Codex CLI installation command and a validation/verification checkpoint (e.g. confirm CHANGELOG.md was updated and entries conform to conventional-commit format) before marking the review complete.

Move the deferred Examples/Troubleshooting content into local references/ files with clearly signaled links, or inline a representative example rather than pointing generically at GitHub.

DimensionReasoningScore

Conciseness

The body is lean and does not explain concepts Claude already knows; the only redundancy is the Overview repeating the frontmatter description verbatim, a minor trim opportunity.

4 / 5

Actionability

Only the install command (`npx skills add -g BenedictKing/codex-review`) is executable; the rest are high-level hints ('Ensure Codex CLI is installed', 'Use /codex-review or natural language triggers') with the specific steps missing, and Examples/Best Practices are generic or deferred to GitHub.

2 / 5

Workflow Clarity

A rough three-step sequence exists but steps are poorly defined (no Codex CLI install method, no trigger examples) and there are no validation or verification checkpoints for the review/CHANGELOG workflow.

2 / 5

Progressive Disclosure

The short, well-sectioned body has no nested references and no bundle files to organize; the only gap is deferring Examples and Troubleshooting to an external GitHub URL rather than a clearly signaled one-level reference.

4 / 5

Total

12

/

20

Passed

Description

50%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 states what the skill does but omits any explicit trigger guidance, so it answers 'what' without 'when'. It is concise and avoids heavy padding, yet the wording leans on generic 'Professional' framing and a broad domain that risks overlap.

Suggestions

Add an explicit 'Use when ...' clause naming natural trigger phrases (e.g. 'Use when reviewing a diff before commit or generating a CHANGELOG from commits').

Replace 'Professional' with a more concrete capability descriptor and list a couple more specific actions (e.g. 'Reviews staged diffs, suggests improvements, and writes CHANGELOG entries').

Sharpen distinctiveness by foregrounding the Codex AI integration and CHANGELOG auto-generation as the differentiators from a generic code-review skill.

DimensionReasoningScore

Specificity

Names the domain ('code review') and two concrete actions ('code review', 'auto CHANGELOG generation') but coverage is not comprehensive, and 'Professional'/'integrated with Codex AI' read as light fluff rather than additional capabilities.

3 / 5

Completeness

Has a clear 'what' (code review + CHANGELOG generation) but no 'when' clause; per the missing-trigger-guidance rule this caps completeness at 3.

3 / 5

Trigger Term Quality

Contains relevant natural keywords ('code review', 'CHANGELOG') a user might say, but misses common variations/synonyms and has no explicit 'Use when...' trigger phrasing.

3 / 5

Distinctiveness Conflict Risk

The Codex AI integration and auto-CHANGELOG give it a niche, but 'Professional code review' is broad and overlaps heavily with existing generic code-review skills.

3 / 5

Total

12

/

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

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
Dokhacgiakhoa/Agent-Skills-4-Vibe-Coding-CLI
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.