hud

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

Quality

65%

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

Quality

Content

77%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 highly actionable with executable commands and a well-validated, clearly sequenced setup workflow including recovery paths. Its weaknesses are token efficiency and progressive disclosure: a large block of reference-style configuration documentation is inlined in the main file instead of split out.

Suggestions

Move the manual-configuration JSON schema, display-elements table, and agentsFormat option catalog into a reference file (e.g. references/config.md) and link to them from a short 'Manual Configuration' section.

Trim the display-rendering explanations (tree characters, agent codes, color-coding tables) to the essentials needed to pick a preset.

Consider condensing the preset examples to the minimal and focused variants, keeping the multi-line 'full' example only in a reference file.

Dimension	Reasoning	Score
Conciseness	The setup steps are command-driven and tight, but the body carries sizable inline reference material Claude rarely needs at execution time — a ~40-line manual-configuration JSON block, the full display-elements/color-coding/agentsFormat tables, and explanations like how tree characters and agent codes render ('Tree characters (├─, └─) show visual hierarchy'). This matches 'mostly efficient but includes some unnecessary explanation or could be tightened'.	3 / 5
Actionability	Every step ships a copy-paste-ready executable command (the node one-liners for existence checks, plugin verification, chmod, legacy cleanup), plus concrete JSON snippets for both Unix and Windows statusLine values. The preset commands and troubleshooting section cover the common cases directly.	5 / 5
Workflow Clarity	Setup is a clearly numbered 7-step sequence with explicit checkpoints (existence check in Step 1, plugin verification in Step 2) and strong feedback loops — a Troubleshooting section with recovery paths for legacy string migration, the Node 24+ 'homedir' SyntaxError, and a manual-verification checklist. Error conditions branch explicitly ('If omc-hud.mjs is MISSING or argument is setup...').	5 / 5
Progressive Disclosure	The section organization is good (Quick Commands, Auto-Setup, Presets, Troubleshooting), but this is a ~250-line body with no bundle files, and content that clearly belongs in a separate reference — the full manual configuration schema, the display-elements table, and agentsFormat option catalog — is inlined in SKILL.md. This is the anchor-3 pattern of structure present but separable content kept inline.	3 / 5
	Total	16 / 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 third-person but thin: it names the domain without concrete actions and provides no 'when to use' trigger guidance. It distinguishes itself mostly through the niche 'HUD' keyword rather than explicit scope.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user mentions the HUD, statusline, or status bar, or wants to change what the OMC status line displays.'

State 1–2 concrete actions beyond category nouns, such as 'installs the HUD statusline wrapper and switches between minimal/focused/full presets'.

Include the natural synonyms users would say — 'statusline', 'status bar', 'set up' — alongside 'HUD'.

Dimension	Reasoning	Score
Specificity	The description names the domain ('HUD display options') and lists a few areas ('layout, presets, display elements'), but these are category nouns rather than concrete actions — comparable to 'Processes PDF files and extracts content', not the multi-action coverage of the 4–5 anchors. It never states what configuring actually entails (installing a statusline script, switching presets, editing settings.json).	3 / 5
Completeness	The 'what' is present ('Configure HUD display options') but there is no 'Use when...' clause or equivalent trigger guidance, which the guidelines explicitly cap at 3. The 'when' is entirely absent rather than weakly implied.	3 / 5
Trigger Term Quality	'HUD', 'display', 'presets', and 'layout' are relevant keywords a user might say, but common variations are missing — most notably 'statusline'/'status bar' (the actual feature being configured) and any phrasing like 'set up' or 'fix the status line'. Matches 'Some relevant keywords but missing common variations or synonyms'.	3 / 5
Distinctiveness Conflict Risk	'HUD' is a fairly niche, well-scoped term that maps cleanly to this statusline skill, giving it a distinct trigger. Minor overlap risk remains with generic statusline/appearance-configuring skills since the description never ties 'HUD' to a statusline or to the OMC plugin, keeping it below the clear-niche anchor 5.	4 / 5
	Total	13 / 20 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
Path: skills/hud/SKILL.md
Commit: dc7ba1d

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