hud

Configure HUD display options (layout, presets, display elements)

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

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 content is highly actionable with executable setup commands and a well-sequenced, validated workflow, but it is over-long for a single file and inlines configuration reference material that would benefit from progressive disclosure into separate files.

Suggestions

Move the full manual configuration JSON and the agentsFormat/callCountsFormat reference into a separate CONFIG.md or reference file, leaving SKILL.md as a concise overview with a clearly signaled link.

Tighten the preset renderings and display-element tables, or relocate the detailed preset/element reference to a dedicated file to reduce inline bulk.

Add an explicit post-edit JSON validation checkpoint in Step 5 (e.g. parse settings.json to confirm valid JSON before instructing a restart) to reinforce the existing feedback loop.

Dimension	Reasoning	Score
Conciseness	The body avoids concept over-explanation and uses tight code blocks, but at ~250 lines it carries bulky inline config JSON and verbose preset galleries that could be tightened or split out.	2 / 3
Actionability	It provides fully executable node one-liners, concrete cp commands from a canonical template, and copy-paste-ready JSON statusLine snippets for both Unix and Windows.	3 / 3
Workflow Clarity	Setup is a clear 7-step sequence with explicit EXISTS/MISSING and READY/NOT_FOUND verification checkpoints, conditional install logic, and a restart-after-change feedback loop.	3 / 3
Progressive Disclosure	Sections are well-organized with clear headers, but the 250+ line body keeps large config JSON, preset galleries, and agent-display details inline rather than splitting them into one-level-deep reference files.	2 / 3
	Total	10 / 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 clearly scopes a specific niche and names concrete option areas, but it omits any explicit "when to use" trigger and relies on a single action verb, capping specificity and completeness at 2.

Suggestions

Add an explicit 'Use when...' clause naming natural user triggers (e.g. 'Use when configuring or repairing the OMC HUD statusline, switching display presets, or adjusting display elements').

Replace the single 'Configure' verb with multiple concrete actions (e.g. 'Install, switch presets, and toggle display elements for the HUD statusline') to raise specificity.

Include common phrasings users would say, such as 'statusline' or 'status bar', to broaden trigger term coverage.

Dimension	Reasoning	Score
Specificity	Names the HUD domain plus concrete option categories ("layout, presets, display elements"), but uses a single verb ("Configure") rather than multiple distinct concrete actions, so it falls short of the multi-action anchor.	2 / 3
Completeness	It states what the skill does but includes no explicit "Use when..." trigger guidance, so per the judging guidelines completeness is capped at 2 even though the "what" is clear.	2 / 3
Trigger Term Quality	Relevant keywords like "HUD", "display options", and the argument-hint presets appear, but common natural phrasings (e.g. "statusline", "change/show HUD") and full variation coverage are missing.	2 / 3
Distinctiveness Conflict Risk	"HUD display options" is a clear, narrow niche tied to a specific statusline component, making it unlikely to trigger for unrelated skills.	3 / 3
	Total	9 / 12 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
referenced_paths_exist	Referenced path issues: 1 missing, 1 deeper-than-1-level	Warning

	Total	14 / 16 Passed

Repository: Yeachan-Heo/oh-my-claudecode
Commit: 6c59219

Reviewed: about 5 hours 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.