Control Philips Hue lights and scenes via the OpenHue CLI.
77
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillEvaluation — 96%
↑ 2.59xAgent success when using this skill
Validation for skill structure
Discovery
40%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 identifies a clear, distinct domain (Philips Hue control via OpenHue CLI) but lacks the completeness needed for effective skill selection. It needs explicit trigger guidance and more specific action verbs to help Claude know when to invoke this skill over others.
Suggestions
Add a 'Use when...' clause with trigger terms like 'turn on lights', 'change light color', 'set scene', 'smart home', 'Hue bridge'
List specific concrete actions such as 'turn lights on/off, adjust brightness, change colors, activate scenes, list available lights'
Include common user phrasings like 'dim the lights', 'set mood lighting', 'control smart lights'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Philips Hue lights) and mentions 'lights and scenes' as targets, but doesn't list specific concrete actions like 'turn on/off', 'adjust brightness', 'change colors', or 'create scenes'. | 2 / 3 |
Completeness | Describes what it does (control Hue lights via OpenHue CLI) 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 'Philips Hue', 'lights', and 'scenes' which are relevant keywords, but misses common variations users might say like 'smart lights', 'home lighting', 'turn on lights', 'change light color', or 'dim lights'. | 2 / 3 |
Distinctiveness Conflict Risk | Very specific niche - Philips Hue and OpenHue CLI are distinct identifiers that are unlikely to conflict with other skills. The combination of brand name and specific tool creates clear differentiation. | 3 / 3 |
Total | 8 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent skill file that exemplifies good practices: concise, actionable commands organized in logical sections with clear scope boundaries. The 'When to Use' and 'When NOT to Use' sections effectively bound the skill's applicability. Quick Presets section adds practical value without bloat.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Lean and efficient with no unnecessary explanations. Every section serves a purpose with concrete commands. No padding about what Hue is or how smart home systems work. | 3 / 3 |
Actionability | Fully executable, copy-paste ready commands throughout. Specific examples cover all common use cases with exact syntax, flags, and parameter ranges (e.g., brightness 0-100, mirek 153-500). | 3 / 3 |
Workflow Clarity | This is a simple, single-purpose skill with clear command patterns. No multi-step destructive operations requiring validation checkpoints. The 'When to Use' and 'When NOT to Use' sections provide clear boundaries. | 3 / 3 |
Progressive Disclosure | Well-organized with logical sections (List Resources → Control Lights → Control Rooms → Scenes → Quick Presets → Notes). Content is appropriately sized for a single file with no need for external references. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
72%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 8 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 8 / 11 Passed | |
Table of Contents
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.