The body is highly actionable and well-organized with concrete commands, config examples, and example preset output; the only real drag is time-sensitive version pinning that could be isolated and minor explanatory padding.

Dimension	Reasoning	Score
Conciseness	Lean tables, code blocks, and preset samples with every section earning its place; minor over-explanation ('Zero code required') and time-sensitive version pins ('Codex CLI v0.101.0+') outside a deprecated section keep it from a 5.	4 / 5
Actionability	Copy-paste-ready commands (`omx hud --watch`, `--json`, `--preset=full`), concrete TOML and JSON config blocks, exact state-file paths, and a numbered troubleshooting sequence fully cover the common cases.	5 / 5
Workflow Clarity	A read-only display skill (no destructive cap), with an unambiguous primary action, a one-command setup, and a numbered diagnostic sequence with an implicit 'if not showing' checkpoint; no explicit validate-fix-retry loop, but one is not strictly required here.	4 / 5
Progressive Disclosure	No bundle files exist and content is fully inline yet well-sectioned (Quick Commands, Presets, Setup, Layer 1/2, Configuration, Color, Troubleshooting) with no nested references; at ~98 lines the 50-line simple-skill 5-exception does not strictly apply, but nothing is buried.	4 / 5
	Total	17 / 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 cleanly states what the skill does and targets a distinct niche, but it lacks any 'when to use it' trigger guidance and relies on generic verbs, leaving completeness and trigger quality at the midpoint.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when the user wants to view OMX orchestration state (ralph, ultrawork, team, pipeline) or configure the statusline.'

Replace generic verbs with concrete capabilities: 'Show OMX orchestration state, switch HUD presets, and configure the Codex statusline.'

Include natural trigger keywords and synonyms users would say, such as 'statusline', 'HUD', 'view modes', 'omx hud', '.omx/state'.

Dimension	Reasoning	Score
Specificity	Names the domain ('OMX HUD', 'two-layer statusline') and two actions ('Show or configure'), but the verbs are generic rather than concrete capabilities like 'reads .omx/state files' or 'configures presets'.	3 / 5
Completeness	A clear 'what' ('Show or configure the OMX HUD (two-layer statusline)') is present, but 'when' is entirely absent — no explicit trigger guidance, which caps completeness at 3 per the rubric.	3 / 5
Trigger Term Quality	Relevant domain keywords ('HUD', 'statusline', 'OMX') a user might say, but missing common variations, synonyms, or file references, and there is no 'Use when...' phrasing.	3 / 5
Distinctiveness Conflict Risk	'OMX HUD (two-layer statusline)' is a narrow product-specific niche with low conflict risk, though the generic 'show or configure' verbs and 'statusline' term leave minor overlap with other statusline skills.	4 / 5
	Total	13 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

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