CtrlK
BlogDocsLog inGet started
Tessl Logo

openhue

Control Philips Hue lights and scenes via the OpenHue CLI.

77

2.59x
Quality

70%

Does it follow best practices?

Impact

96%

2.59x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./skills/openhue/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

This is a well-crafted skill that serves as a clean, actionable CLI reference. It's concise, provides executable commands with realistic parameters, and is well-organized with clear scoping of when to use it. The Quick Presets section adds practical value by showing common real-world combinations.

DimensionReasoningScore

Conciseness

The skill is lean and efficient. It doesn't explain what Philips Hue is or how CLI tools work. Every section serves a purpose with concrete commands and no filler text. The 'When to Use' / 'When NOT to Use' sections are appropriately brief and help scope the skill.

3 / 3

Actionability

Every command is fully executable and copy-paste ready with realistic examples. Parameters are shown with clear value ranges (e.g., brightness 0-100, mirek 153-500), and multiple variations are demonstrated for each operation type.

3 / 3

Workflow Clarity

This is a simple, single-purpose skill (CLI command reference) without destructive or batch operations. The commands are clearly organized by category (list, control lights, rooms, scenes, presets), and the notes section covers prerequisites like bridge pairing. No multi-step workflow requiring validation checkpoints exists here.

3 / 3

Progressive Disclosure

For a skill under 50 lines of substantive content with no need for external references, the organization is excellent. Content is well-structured with clear section headers, and the scope is appropriate for a single file without requiring supplementary documents.

3 / 3

Total

12

/

12

Passed

Description

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, dim, change color, set scenes) and critically omits a 'Use when...' clause that would help Claude know when to select this skill.

Suggestions

Add a 'Use when...' clause, e.g., 'Use when the user asks to control smart lights, turn on/off Philips Hue bulbs, adjust brightness, change light colors, or activate lighting scenes.'

List specific concrete actions such as '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' to improve keyword coverage.

DimensionReasoningScore

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 'Use when...' clause or equivalent explicit trigger guidance, which per the rubric caps completeness at 2, and the 'what' itself 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

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.

Validation8 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

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
attilaczudor/Test
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.