CtrlK
BlogDocsLog inGet started
Tessl Logo

code-review

Run a comprehensive code review

56

Quality

63%

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 ./plugins/oh-my-codex/skills/code-review/SKILL.md
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.

The body is highly actionable with concrete prompts, commands, deterministic gating, and clear workflows, but it is a large monolithic file with some redundancy and no progressive disclosure into bundle references.

Suggestions

Split large inline blocks (review/architect checklists, the output template, the Codex consultation protocol) into separate reference files linked from SKILL.md.

De-duplicate the merge-gating rules and approval criteria, which are restated in both the synthesis step and the Approval Criteria section.

Tighten explanatory passages (e.g., the GPT-5.6 guidance and State/HUD contract) to keep the body lean.

DimensionReasoningScore

Conciseness

Most content earns its place (executable prompts, commands, templates), but gating rules and checklists are restated across sections and a few passages could be tightened, leaving it mostly efficient rather than fully lean.

2 / 3

Actionability

It provides fully executable task() prompts, a concrete omx state command, deterministic merge-gating rules, and a copy-paste output template rather than vague direction or pseudocode.

3 / 3

Workflow Clarity

A clear 7-step sequence pairs with explicit approval gating and fallback rules for unavailable lanes, giving this merge-readiness gate concrete validation checkpoints and feedback loops.

3 / 3

Progressive Disclosure

Sections are well-organized, but the skill is a large single-file monolith with no bundle files and no external references, leaving content that could be split (checklists, output template, consultation protocol) inline.

2 / 3

Total

10

/

12

Passed

Description

50%

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 clear about the core task but stays at a high level, naming the domain without enumerating specific actions or providing explicit use-when triggers. It is distinguishable but would benefit from concrete actions and trigger phrases.

Suggestions

Add a "Use when..." clause listing natural trigger phrases such as "review this code", "before merging a pull request", or "assess code quality".

Enumerate specific concrete actions, e.g. "find security vulnerabilities, rate issue severity, and verify merge readiness".

Include common user phrasings/variations ("code review", "check my code", "PR review") to strengthen trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain and one action ("Run a comprehensive code review") but lists no specific concrete actions such as severity rating or security checks, so it falls between the vague anchor and a multi-action list.

2 / 3

Completeness

It states what the skill does but omits any explicit "Use when..." trigger clause, which per the guidelines caps completeness at 2.

2 / 3

Trigger Term Quality

"code review" is a natural term users say, but common variations like "review this code", "check my code", or "merge readiness" are missing, giving partial rather than full coverage.

2 / 3

Distinctiveness Conflict Risk

"code review" is a reasonably clear niche and distinguishable, but the brief description lacks distinctive framing that would fully separate it from general review skills.

2 / 3

Total

8

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Yeachan-Heo/oh-my-codex
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.