hud

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

Quality

66%

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

78%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 content is highly actionable with executable commands and a well-sequenced, checkpointed setup workflow, plus clearly marked legacy/deprecated sections. Its main weakness is progressive disclosure: it is a long monolithic file with no external references for the bulky config and preset material.

Suggestions

Move the large manual-configuration JSON reference and full preset display examples into a separate references file (e.g. references/HUD_CONFIG.md) and link to it from the body.

De-duplicate the statusLine object JSON (shown in both Step 5 and Troubleshooting) to trim tokens.

Add an explicit post-edit validation step (e.g. parse settings.json as JSON) to Step 5 to close the workflow feedback loop.

Dimension	Reasoning	Score
Conciseness	The body is mostly dense commands and tables with no concept padding, though the statusLine object JSON is repeated (Step 5 and Troubleshooting) and some cross-platform prose could be trimmed.	4 / 5
Actionability	It provides fully executable, copy-paste-ready `node -e`/bash commands, exact JSON config, and concrete file paths covering setup, preset switching, manual config, and troubleshooting.	5 / 5
Workflow Clarity	The 7-step setup has a clear sequence with existence/verification checkpoints and error-recovery guidance, but Step 5's settings.json edit lacks an explicit post-edit validity check, keeping it just below the top anchor.	4 / 5
Progressive Disclosure	No bundle files exist and the ~251-line body is monolithic with no external references; it is well-sectioned but inlines reference material (full config JSON, preset examples) that could live in separate files, beyond the simple-skill <50-line exception.	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 specific and recognizable but lacks any trigger guidance, which caps its completeness and leaves it without a clear "when to use" signal. Trigger terms are present but thin on natural synonyms.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when configuring the OMC HUD statusline or switching display presets.'

Replace generic verbs with concrete actions (e.g. 'Install, switch presets, and toggle HUD display elements') to raise specificity.

Include natural user phrases and synonyms like 'statusline', 'HUD layout', or 'change what the HUD shows'.

Dimension	Reasoning	Score
Specificity	Names the domain ("HUD display options") and enumerates concrete sub-areas ("layout, presets, display elements"), but uses a single generic verb ("Configure") rather than multiple distinct actions, fitting below the multiple-action anchor of 4.	3 / 5
Completeness	It gives a clear "what" (configure HUD display options) but includes no "Use when..." or equivalent trigger guidance, so per the rubric completeness caps at 3.	3 / 5
Trigger Term Quality	"HUD" and "display" are natural user terms, but "layout, presets, display elements" lean technical/config and common synonyms or variations are missing, matching the some-keywords-but-incomplete anchor.	3 / 5
Distinctiveness Conflict Risk	The "HUD" niche is fairly distinctive and unlikely to trigger for unrelated skills, with only minor overlap risk against other display/config skills.	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: 5aa678c

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