hud

Show or configure the OMX HUD (two-layer statusline)

Quality

71%

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/hud/SKILL.md

Quality

Content

85%

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 and well-organized with executable commands and real config examples, scoring top marks on actionability, workflow clarity, and progressive disclosure. Its only weakness is conciseness, due to inline version pinning that would be better isolated.

Suggestions

Move the 'Codex CLI v0.101.0+' version requirement into a dedicated compatibility/deprecated section so time-sensitive info does not clutter the main guidance.

Consider trimming the long one-line list of available built-in statusLine items into a compact reference or a separate file as the skill grows.

Add a brief verification step to Setup (e.g. 'Confirm the statusline renders after restart') to make the workflow checkpoint explicit.

Dimension	Reasoning	Score
Conciseness	The body is dense and reference-style with no concept padding, but pins time-sensitive version info ('Codex CLI v0.101.0+') inline and includes a long list of built-in items that could be tightened.	2 / 3
Actionability	Provides concrete, copy-paste-ready commands (omx hud --watch/--json/--preset), real TOML and JSON config blocks, and explicit state-file paths throughout.	3 / 3
Workflow Clarity	Setup and troubleshooting are clearly sequenced with a concrete recovery procedure and a branch for the 'No active modes' case; as a low-risk display skill it does not require a destructive-feedback loop.	3 / 3
Progressive Disclosure	No bundle files exist, so content is appropriately self-contained in well-organized, clearly headed sections with no nested references.	3 / 3
	Total	11 / 12 Passed

Description

57%

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 distinct but only partially complete: it conveys what the skill does without any explicit trigger guidance for when to use it. Adding a 'Use when...' clause would raise completeness and trigger-term coverage.

Suggestions

Add a 'Use when...' clause with natural trigger phrases, e.g. 'Use when the user asks to show or change the OMX HUD, statusline, status bar, or display mode info.'

Expand 'configure' into concrete actions (e.g. switch presets, edit hud-config.json) so the capability list is comprehensive.

Include common synonyms like 'status bar', 'status line', and 'display' alongside 'HUD' and 'statusline' for better trigger coverage.

Dimension	Reasoning	Score
Specificity	Names two concrete actions ('Show', 'configure') and a specific object ('OMX HUD', 'two-layer statusline'), but does not enumerate what configuration entails, so it is not comprehensive.	2 / 3
Completeness	Clearly states what the skill does but provides no 'Use when...' or equivalent explicit trigger guidance, capping completeness at 2 per the rubric.	2 / 3
Trigger Term Quality	Includes relevant natural terms ('HUD', 'statusline') but lacks common variations like 'status bar' or 'status line' and has no keyword list of when users would invoke it.	2 / 3
Distinctiveness Conflict Risk	The 'OMX HUD (two-layer statusline)' niche is specific and named, making it unlikely to trigger for unrelated skills.	3 / 3
	Total	9 / 12 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: plugins/oh-my-codex/skills/hud/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.