eightctl
Control Eight Sleep pods (status, temperature, alarms, schedules).
69
61%
Does it follow best practices?
Impact
83%
2.07xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/eightctl/SKILL.mdQuality
Discovery
50%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 is concise and names a specific product with concrete actions, giving it strong specificity and distinctiveness. However, it lacks a 'Use when...' clause, which significantly hurts completeness and could make it harder for Claude to know when to select this skill. Adding natural user trigger terms like 'smart bed', 'mattress temperature', or 'bed cooling' would also improve discoverability.
Suggestions
Add a 'Use when...' clause, e.g., 'Use when the user asks about their Eight Sleep pod, bed temperature, sleep schedule, or smart mattress settings.'
Include natural trigger term variations users might say, such as 'smart bed', 'mattress cooling/heating', 'bed temperature', or 'sleep tracking'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: status, temperature, alarms, and schedules. These are clear, distinct capabilities related to Eight Sleep pod control. | 3 / 3 |
Completeness | Describes what the skill does (control Eight Sleep pods) but completely lacks a 'Use when...' clause or any explicit trigger guidance. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and since the 'when' is entirely absent, this scores a 1. | 1 / 3 |
Trigger Term Quality | Includes 'Eight Sleep pods', 'temperature', 'alarms', 'schedules', and 'status' which are relevant keywords. However, it misses common user variations like 'bed', 'mattress', 'sleep tracking', 'bed cooling/heating', or 'smart bed'. | 2 / 3 |
Distinctiveness Conflict Risk | Eight Sleep pods are a very specific product niche. The description is clearly distinguishable from other skills and unlikely to conflict with anything else. | 3 / 3 |
Total | 9 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a concise, well-structured CLI reference skill that efficiently covers the basics of eightctl usage. Its main weakness is incomplete actionability for complex subcommands—the skill lists commands like `alarm create` and `schedule create` without showing required arguments or example invocations. The safety note about confirming before changes is good but could be more explicitly integrated into a workflow.
Suggestions
Add example invocations with arguments for complex subcommands, e.g., `eightctl alarm create --time 07:00 --days mon,wed,fri` and `eightctl schedule create --start 22:00 --temp -5`
Show expected output for `eightctl status` so Claude knows what information is available and how to interpret it
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. Every line serves a purpose—no explanations of what Eight Sleep is, no unnecessary context. Assumes Claude knows how CLI tools and config files work. | 3 / 3 |
Actionability | Provides concrete CLI commands that are copy-paste ready, but lacks examples of full command syntax for more complex operations (e.g., `alarm create` arguments, `schedule create` parameters, `base angle` values). The commands are listed but incomplete for non-trivial tasks. | 2 / 3 |
Workflow Clarity | The skill mentions confirming before changing temperature or alarms (a safety checkpoint), but there's no explicit workflow sequence for multi-step operations like creating schedules or alarms. For a CLI wrapper skill this is relatively simple, but the 'confirm before changing' note is implicit rather than structured as a validation step. | 2 / 3 |
Progressive Disclosure | For a simple, single-purpose CLI skill under 50 lines with no bundle files, the content is well-organized into logical sections (auth, quick start, common tasks, notes) and doesn't need external references. | 3 / 3 |
Total | 10 / 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
- attilaczudor/Test
- Commit
b4fc4af
- 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.