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 critically lacks any 'Use when...' guidance, which would help Claude know when to select this skill from a large pool. Adding natural user trigger terms like 'smart bed', 'bed temperature', or 'sleep pod' 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 schedules, or smart mattress settings.'
Include common user-facing synonyms and variations such as 'smart bed', 'bed cooling/heating', 'mattress temperature', or 'sleep pod' to improve trigger term coverage.
| 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 but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, 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', 'bed heating', or 'smart bed'. | 2 / 3 |
Distinctiveness Conflict Risk | Very clear niche — 'Eight Sleep pods' is a specific product/brand, making it highly unlikely to conflict with other skills. The triggers are distinct and narrowly scoped. | 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 skill that efficiently communicates the basics of the eightctl CLI. Its main weakness is incomplete actionability—commands are listed but lack argument formats, valid ranges, and example outputs. The workflow could benefit from explicit validation steps after destructive operations like temperature changes.
Suggestions
Add argument details for key commands (e.g., valid temperature range for `eightctl temp`, required fields for `eightctl alarm create` and `eightctl schedule create`)
Add a brief validation pattern: e.g., after `eightctl temp 20`, run `eightctl status` to confirm the change took effect
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. Every line provides actionable information with zero unnecessary explanation. No padding or concepts Claude already knows. | 3 / 3 |
Actionability | Provides concrete CLI commands that are copy-paste ready, but lacks details on command arguments (e.g., what format does alarm create expect? what are valid temp ranges? what does schedule create need?). The commands are listed but incomplete for full execution. | 2 / 3 |
Workflow Clarity | For a simple CLI tool this is mostly adequate, but the note to 'confirm before changing temperature or alarms' is vague and there's no explicit validation step (e.g., check status after setting temp). Multi-step workflows like creating schedules or alarms have no sequencing guidance. | 2 / 3 |
Progressive Disclosure | For a simple, short skill under 50 lines with a single-purpose CLI tool, the content is well-organized into logical sections (auth, quick start, common tasks, notes) with clear navigation. No need for 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
b3cef5f
- 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.