hud
Configure HUD display options (layout, presets, display elements)
43
43%
Does it follow best practices?
Impact
—
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 sense of what the skill does—configuring HUD display options—but lacks depth in concrete actions and entirely omits trigger guidance ('Use when...'). The parenthetical list hints at capabilities but reads more like a category summary than actionable specifics, and the absence of context about when to invoke this skill significantly weakens its utility for skill selection.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user wants to customize their HUD layout, toggle display elements, or manage HUD presets.'
Expand the concrete actions beyond the parenthetical, e.g., 'Configures HUD display settings including arranging layout positions, creating and applying presets, and toggling individual display elements such as minimap, health bar, or notifications.'
Include natural trigger term variations users might say, such as 'heads-up display', 'HUD settings', 'screen overlay', or 'UI customization'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (HUD display) and lists some actions (configure layout, presets, display elements), but the parenthetical list is more of a category enumeration than concrete specific actions like 'create preset layouts' or 'toggle individual display elements'. | 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, missing 'Use when' should cap completeness at 2, and since the 'what' is also fairly thin, this scores a 1. | 1 / 3 |
Trigger Term Quality | Includes relevant terms like 'HUD', 'display', 'layout', 'presets', and 'display elements', which are somewhat natural but domain-specific. Missing common variations users might say like 'heads-up display', 'UI overlay', 'screen layout', or 'HUD 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 other UI/display configuration skills. The lack of explicit context (e.g., which application or game) reduces distinctiveness. | 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 verbosity—the full configuration reference, display preset details, agent format options, and troubleshooting are all inlined creating a massive document. This content would benefit greatly from splitting into a quick-start overview with references to detailed configuration and troubleshooting files.
Suggestions
Extract the full configuration JSON, agentsFormat options, and display element tables into a separate HUD-CONFIG-REFERENCE.md file, keeping only the quick commands and setup steps in SKILL.md
Move troubleshooting content to a separate TROUBLESHOOTING.md and reference it with a single link
Condense the inline Node.js one-liners in Steps 1-2 by referencing a diagnostic script rather than embedding complex JavaScript in bash commands
Remove the Display Elements table and Color Coding section—these describe runtime output that Claude doesn't need to configure, or move them to a reference file
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~200+ lines. It includes extensive inline setup instructions with long one-liner Node.js scripts, detailed explanations of display elements Claude could infer, and configuration JSON that could be in a separate reference file. Much of this content (color coding descriptions, element tables, agent format options) could be drastically condensed. | 1 / 3 |
Actionability | The skill provides fully executable bash and Node.js commands for every step, concrete JSON configuration examples for both Unix and Windows, and specific file paths. Commands are copy-paste ready with proper environment variable handling. | 3 / 3 |
Workflow Clarity | The setup process is clearly sequenced as Steps 1-7 with explicit validation checkpoints (check if setup needed, verify plugin installed, confirm existence). 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 everything inline. The full manual configuration JSON, all agent format options, display element tables, color coding details, and troubleshooting could all be split into separate reference files. No external references are used despite the content clearly warranting them. | 1 / 3 |
Total | 8 / 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
679b418
- 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.