omx-setup

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

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/omx-setup/SKILL.md

Quality

Content

92%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 a dense, well-structured task card with executable commands, explicit validation, and error-recovery guidance. It is among the stronger content examples, with only minor conciseness trimming possible.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence, with flag semantics that earn their place; it is not perfectly terse, with a few dense option descriptions that could be trimmed.	4 / 5
Actionability	It provides fully executable, copy-paste-ready commands (omx setup, omx doctor, npm run build, node dist/cli/omx.js ...) covering the common install/verify cases.	5 / 5
Workflow Clarity	A numbered Resolve sequence is paired with an explicit Verify/doctor checkpoint and an error-recovery feedback loop (rerun with --force/--merge-agents, rerun the smallest corrective command), with a clear stop condition.	5 / 5
Progressive Disclosure	Content is organized into clear sections with a single well-signaled one-level reference to templates/AGENTS.md for shared rules; no nested references and no bundle files are needed for this short task card.	5 / 5
	Total	19 / 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 concise and names a specific, distinguishable tool, but it lacks any explicit "Use when" trigger guidance and only hints at the actions involved. It is functional but underspecified for triggering.

Suggestions

Add an explicit trigger clause, e.g. "Use when installing or refreshing oh-my-codex for a project or user scope."

List a couple more concrete actions or outcomes (e.g. "install, refresh, or migrate OMX config") to raise specificity.

Include natural synonyms users might say (install, initialize, refresh) alongside "setup" and "configure".

Dimension	Reasoning	Score
Specificity	Names the domain (oh-my-codex) and two concrete actions ("Setup and configure") but offers no broader coverage of what configuration entails, matching the 1-2-concrete-actions anchor.	3 / 5
Completeness	It states a clear "what" (setup and configure oh-my-codex) but provides no "Use when..." trigger clause, which caps completeness at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	"Setup" and "configure" are natural terms a user might say, but common variations or synonyms (e.g. install, initialize, refresh) are missing.	3 / 5
Distinctiveness Conflict Risk	Naming the specific tool oh-my-codex gives it a clear niche with low overlap risk, though the absence of distinct trigger phrases keeps it just below a 5.	4 / 5
	Total	13 / 20 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: Yeachan-Heo/oh-my-codex
Path: skills/omx-setup/SKILL.md
Commit: 1dcf513

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.