hud

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

Quality

43%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/hud/SKILL.md

Quality

Discovery

32%

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 provides a basic sense of what the skill does—configuring HUD display options—but lacks specificity in its listed capabilities and entirely omits explicit trigger guidance ('Use when...'). The domain is somewhat niche (HUD configuration), which helps with distinctiveness, but the description would benefit significantly from concrete actions and explicit usage triggers.

Suggestions

Add a 'Use when...' clause with trigger terms like 'Use when the user wants to customize their HUD, adjust heads-up display layout, change on-screen elements, or manage display presets'.

List more specific concrete actions, e.g., 'toggle display elements (health bar, minimap, compass), arrange HUD layout positions, save and load display presets'.

Include natural keyword variations users might say, such as 'heads-up display', 'UI overlay', 'on-screen interface', or 'screen layout'.

Dimension	Reasoning	Score
Specificity	Names the domain (HUD display) and lists some actions (configure layout, presets, display elements), but these are somewhat vague categories rather than concrete specific actions like 'add minimap overlay' or 'toggle health bar visibility'.	2 / 3
Completeness	Describes what the skill does (configure HUD display options) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, a missing 'Use when...' clause should cap completeness at 2, and since the 'what' is also only moderately clear, this scores a 1.	1 / 3
Trigger Term Quality	Includes relevant terms like 'HUD', 'display', 'layout', 'presets', and 'display elements', which are reasonably natural. However, it misses common variations users might say such as 'heads-up display', 'UI overlay', 'screen elements', or 'interface settings'.	2 / 3
Distinctiveness Conflict Risk	The HUD-specific focus provides some distinctiveness, but 'display options' and 'layout' are generic enough to potentially overlap with general UI configuration or settings-related skills.	2 / 3
	Total	7 / 12 Passed

Implementation

55%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill is highly actionable with clear, executable commands and a well-sequenced setup workflow with validation steps. However, it suffers significantly from being a monolithic document that tries to cover everything inline—setup, configuration reference, display presets, troubleshooting, and platform-specific variations—resulting in poor token efficiency and no progressive disclosure. The content would benefit greatly from splitting into a concise overview with references to detailed sub-documents.

Suggestions

Extract the full configuration JSON reference, agentsFormat options, and display elements table into a separate REFERENCE.md file, keeping only the quick commands and setup steps in SKILL.md

Move troubleshooting content to a separate TROUBLESHOOTING.md or consolidate it with the omc-doctor skill reference

Remove explanatory text that Claude can infer (e.g., color coding descriptions, what tree characters mean, what each display element shows) and keep only the preset examples as visual references

Consolidate the platform-specific (Unix vs Windows) instructions into a single conditional block rather than repeating JSON examples for each platform

Dimension	Reasoning	Score
Conciseness	The skill is extremely verbose at ~200+ lines. It includes extensive inline setup scripts, detailed configuration JSON with every option, multiple platform-specific variations, and explanations of display elements that Claude could infer. Much of this content (color coding descriptions, element tables, agent format options) could be in separate reference files.	1 / 3
Actionability	The skill provides fully executable bash and node commands for every step, concrete JSON configuration examples, specific file paths, and copy-paste ready commands for both Unix and Windows. The setup instructions are precise and complete.	3 / 3
Workflow Clarity	The setup workflow is clearly sequenced as Steps 1-7 with explicit validation checkpoints (check if exists, verify plugin installed, then install, then configure). The auto-setup section explains the decision logic, and troubleshooting provides a clear escalation path with feedback loops.	3 / 3
Progressive Disclosure	This is a monolithic wall of text with no references to external files for detailed content. The full configuration JSON, all agent format options, display element tables, color coding, and troubleshooting are all inline. The configuration reference, display presets, and agent format details should be in separate files with clear links from the overview.	1 / 3
	Total	8 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

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

	Total	10 / 11 Passed

Repository: Yeachan-Heo/oh-my-claudecode
Commit: 3e94567

Reviewed: 1 day 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.