CtrlK
BlogDocsLog inGet started
Tessl Logo

omx-setup

Setup and configure oh-my-codex using current CLI behavior

60

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/oh-my-codex/skills/omx-setup/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

88%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 skill body is highly actionable, lean, and well-sequenced with explicit validation and error-recovery feedback loops appropriate to a setup/mutation operation. Progressive disclosure is strong with clear sectioning and no nested references.

DimensionReasoningScore

Conciseness

The body is dense and assumes Claude's CLI competence, with no concept padding; the only trim candidate is the long --merge-agents flag paragraph, placing it just below the leanest anchor.

4 / 5

Actionability

It provides copy-paste-ready commands (omx setup with full flag set, omx doctor, build/verify commands) and concrete troubleshooting commands covering the common cases.

5 / 5

Workflow Clarity

A clear sequenced workflow (Resolve setup -> What changes -> Verify) with explicit validation (omx doctor), feedback loops (rerun with --force/--merge-agents if AGENTS not overwritten), and an exit-contract checklist for a mutation operation.

5 / 5

Progressive Disclosure

Content is well-organized into clearly headed sections with one-level runtime path references (templates/AGENTS.md, skill paths); no bundle files exist, and structure is good though slightly over the simple-skill line count.

4 / 5

Total

18

/

20

Passed

Description

53%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 clear and domain-specific but lacks an explicit 'when to use' trigger clause and broader keyword coverage, which cap its completeness and trigger quality at mid-range. It is distinct within the oh-my-codex niche with only minor sibling-skill overlap.

Suggestions

Add an explicit 'Use when...' clause with concrete trigger phrases, e.g. 'Use when installing or refreshing OMX for a project or user scope.'

Include natural synonyms users actually say — 'install', 'refresh', and the 'omx' abbreviation — to broaden trigger keyword coverage.

Tighten 'Setup and configure' into more specific actions (e.g. 'install, refresh, and configure oh-my-codex CLI artifacts') to lift specificity above 3.

DimensionReasoningScore

Specificity

The description names the domain ('oh-my-codex') and two actions ('Setup and configure') but they are generic verbs with no concrete sub-tasks, matching the anchor for 1-2 concrete actions that are not comprehensive.

3 / 5

Completeness

It states clearly what the skill does ('Setup and configure oh-my-codex using current CLI behavior') but has no 'Use when...' trigger clause, and the rubric caps completeness at 3 when explicit trigger guidance is missing.

3 / 5

Trigger Term Quality

'Setup' and 'configure' are natural user terms, but the description omits common variations/synonyms used elsewhere in the skill (install, refresh, omx abbreviation), so keyword coverage is partial rather than good.

3 / 5

Distinctiveness Conflict Risk

The oh-my-codex niche and setup/configure triggers are mostly distinct, but there is minor overlap risk with sibling omx-* skills (e.g. omx doctor, other omx task cards) referenced in the body.

4 / 5

Total

13

/

20

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.