hud
Configure HUD display options (layout, presets, display elements)
63
55%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/hud/SKILL.mdQuality
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 understanding of the skill's purpose but lacks explicit trigger guidance, which is critical for skill selection. The parenthetical list hints at capabilities without fully articulating them, and the absence of a 'Use when...' clause significantly limits its effectiveness in a multi-skill environment.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user wants to customize HUD appearance, change display layout, or manage HUD presets'
Expand the capability list into full phrases: 'Configures HUD display options including adjusting layout positioning, creating and applying presets, and toggling display elements'
Include natural keyword variations such as 'heads-up display', 'on-screen display', 'UI overlay', or 'interface customization'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (HUD display) and lists some actions (layout, presets, display elements), but these are parenthetical hints rather than fully described concrete actions like 'adjust layout positioning' or 'save custom presets'. | 2 / 3 |
Completeness | Describes what it does (configure HUD options) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes relevant terms like 'HUD', 'display', 'layout', 'presets' that users might say, but missing common variations like 'heads-up display', 'UI configuration', 'screen elements', or 'interface settings'. | 2 / 3 |
Distinctiveness Conflict Risk | 'HUD display' is somewhat specific and distinguishes from general UI or settings skills, but 'display options' and 'layout' could overlap with other configuration or UI-related skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a functional, actionable skill with clear step-by-step setup instructions and executable code. Its main weakness is the monolithic structure - the inline JavaScript wrapper script and extensive configuration documentation inflate the token count significantly. The workflow is well-sequenced with proper validation steps, but the content would benefit from splitting advanced configuration and the wrapper script into separate reference files.
Suggestions
Move the 80-line omc-hud.mjs wrapper script to a separate file (e.g., HUD-WRAPPER.md or templates/omc-hud.mjs) and reference it from the main skill
Split the Manual Configuration section and detailed element/threshold options into a separate HUD-CONFIG-REFERENCE.md file
Condense the Display Presets section - the examples are helpful but could be more compact by removing redundant explanations
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is moderately efficient but includes some verbose sections like the full 80-line JavaScript wrapper script inline, detailed configuration examples, and explanations that could be more condensed. The troubleshooting section and manual configuration could be moved to separate files. | 2 / 3 |
Actionability | Provides fully executable bash commands and complete JavaScript code. The setup instructions are copy-paste ready with specific node one-liners for each step, and the JSON configuration examples are concrete and complete. | 3 / 3 |
Workflow Clarity | Clear 6-step setup process with explicit validation checkpoints (Step 1 checks if setup needed, Step 2 verifies plugin installation). Each step has a clear purpose and the sequence handles conditional logic (Unix vs Windows, missing vs existing files). | 3 / 3 |
Progressive Disclosure | The skill is a monolithic document with all content inline. The 80-line JavaScript wrapper script, detailed configuration options, and troubleshooting could be split into separate reference files. The Quick Commands table provides good overview, but advanced content isn't properly separated. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%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
48ffaac
- Reviewed
Table of Contents
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.