omx-setup

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

Quality

63%

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

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 actionable with concrete commands and a clear verified workflow, but it is a long monolithic document whose dense behavioral notes and flag prose are verbose and would benefit from tightening and splitting into reference material.

Suggestions

Tighten 'Important behavior notes' and the flag bullet list into shorter declarative statements; remove redundant caveats that repeat across sections.

Move the detailed flag/policy/migration reference material into a bundled reference file (e.g. references/flags.md) and keep SKILL.md as a concise overview with a one-level-deep pointer.

Consolidate the overlapping scope/install-mode resolution prose in 'What this setup actually does' and 'Important behavior notes' to avoid restating the same rules twice.

Dimension	Reasoning	Score
Conciseness	The body is mostly useful operational detail rather than concepts Claude already knows, but it is heavily padded with long caveated sentences in 'Important behavior notes' and dense flag descriptions that could be tightened considerably; not a score-3 lean doc.	2 / 3
Actionability	It provides concrete, copy-paste-ready commands (the full omx setup flag block, 'omx setup --force --verbose', 'omx doctor', 'node bin/omx.js setup ...', 'npm run build') with specific examples and verification indicators.	3 / 3
Workflow Clarity	The 'Recommended workflow' is a clear sequence (run setup -> verify with omx doctor -> start Codex) with an explicit validation checkpoint and 'Expected verification indicators', plus a troubleshooting/missing-skill recovery path that acts as a feedback loop.	3 / 3
Progressive Disclosure	No bundle files exist (references/scripts/assets absent) and the skill is a single ~140-line monolithic document; sections are well-labeled, but the dense behavioral/policy/migration notes are inline content that could be split into reference files rather than kept in the overview.	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 names the domain and a couple of actions but is thin: it lacks an explicit use-when trigger, broader natural trigger terms, and a fuller enumeration of setup capabilities.

Suggestions

Add an explicit 'Use when ...' clause listing natural triggers such as installing, refreshing, or reconfiguring oh-my-codex/omx for a project or user scope.

Enumerate concrete capabilities (e.g., resolve scope, choose plugin vs legacy delivery, merge AGENTS.md, run omx doctor) rather than only 'setup and configure'.

Replace 'current CLI behavior' with user-facing phrasing and include common variations users would actually say (install, refresh, init, omx setup).

Dimension	Reasoning	Score
Specificity	Names the domain (oh-my-codex) and two actions ("Setup and configure"), but does not enumerate the concrete operations (install, refresh scopes, plugin/legacy delivery, AGENTS.md merge), so it is not comprehensive.	2 / 3
Completeness	It states what the skill does (setup and configure oh-my-codex) but provides no "Use when..." trigger guidance, so per the rubric a missing explicit when-clause caps completeness at 2.	2 / 3
Trigger Term Quality	"Setup and configure" and "oh-my-codex" are usable natural terms, but common variations users would say (install, refresh, init, omx setup) are missing and "current CLI behavior" reads as internal jargon.	2 / 3
Distinctiveness Conflict Risk	oh-my-codex setup is a specific niche, but the bare "setup and configure" wording could overlap with sibling omx-* skills and lacks triggers that would make it unambiguously the right match.	2 / 3
	Total	8 / 12 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: plugins/oh-my-codex/skills/omx-setup/SKILL.md
Commit: 435d4a9

Reviewed: 2 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.