openhue
Control Philips Hue lights and scenes via the OpenHue CLI.
77
70%
Does it follow best practices?
Impact
96%
2.59xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./openclaw/skills/openhue/SKILL.mdQuality
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 and distinctive niche (Philips Hue control via OpenHue CLI) but is too terse. It lacks specific concrete actions (e.g., toggle lights, set brightness, change colors, activate scenes) and has no explicit 'Use when...' clause to guide skill selection.
Suggestions
Add a 'Use when...' clause such as 'Use when the user asks to control smart lights, turn on/off Hue lights, change light colors or brightness, or activate lighting scenes.'
List specific concrete actions like 'Turn lights on/off, adjust brightness and color, activate scenes, list rooms and devices' to improve specificity.
Include natural trigger term variations like 'smart lights', 'bulbs', 'brightness', 'color', 'turn on', 'turn off' that users would commonly say.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Philips Hue lights) and some actions ('control lights and scenes'), but doesn't list specific concrete actions like turning on/off, adjusting brightness, changing colors, listing rooms, etc. | 2 / 3 |
Completeness | Describes what it does ('Control Philips Hue lights and scenes via the OpenHue CLI') but has no explicit 'Use when...' clause or equivalent trigger guidance, which per the rubric caps completeness at 2, and the 'what' is also fairly thin, placing this at 1. | 1 / 3 |
Trigger Term Quality | Includes good trigger terms like 'Philips Hue', 'lights', and 'scenes', but misses common variations users might say such as 'smart lights', 'turn on/off lights', 'brightness', 'color', 'rooms', 'bulbs', or 'lighting'. | 2 / 3 |
Distinctiveness Conflict Risk | Very clear niche — Philips Hue lights via OpenHue CLI is highly specific and unlikely to conflict with other skills. The combination of brand name, device type, and specific CLI tool makes it distinctly identifiable. | 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 is concise, well-organized, and highly actionable. It provides complete, executable CLI commands covering all common Hue control scenarios without any unnecessary explanation. The 'When to Use / When NOT to Use' routing guidance and quick presets add practical value beyond a bare command reference.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient. The 'When to Use' and 'When NOT to Use' sections add value for routing decisions without over-explaining. Every section contains actionable commands with no unnecessary prose or concept explanations. | 3 / 3 |
Actionability | Every command is fully executable and copy-paste ready with realistic examples covering lights, rooms, scenes, brightness, color, and temperature. The quick presets section provides concrete real-world usage patterns. | 3 / 3 |
Workflow Clarity | This is a simple, single-purpose skill (CLI command reference) with no multi-step destructive operations. Commands are clearly categorized and unambiguous. The notes section covers prerequisites (bridge pairing, network). No feedback loops are needed for these non-destructive operations. | 3 / 3 |
Progressive Disclosure | For a skill under 50 lines of substantive content, the organization is excellent with clear section headers (List Resources, Control Lights, Control Rooms, Scenes, Quick Presets, Notes) that enable quick scanning and discovery without needing external files. | 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 | |
- Repository
- trpc-group/trpc-agent-go
- Commit
0c1ec2b
- 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.