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 clear product domain (Eight Sleep pods) with specific actions, making it distinctive. However, it critically lacks a 'Use when...' clause, which hurts completeness and could make it harder for Claude to know when to select this skill. Adding natural user trigger terms like 'smart bed', 'bed temperature', or 'sleep schedule' 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 common user-facing synonyms and variations such as 'smart bed', 'bed cooling/heating', 'mattress temperature', or 'sleep tracking' 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. 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', 'bed heating', or 'smart bed'. | 2 / 3 |
Distinctiveness Conflict Risk | 'Eight Sleep pods' is a very specific product niche with distinct triggers. It is highly unlikely to conflict with other skills given the branded product name and specific IoT control actions. | 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.
A very concise and well-structured CLI reference skill that efficiently covers the basics of eightctl. Its main weakness is incomplete actionability—common tasks like alarm creation and schedule management list subcommands but don't show their required arguments or expected outputs. Adding a verification step after state-changing operations would also improve workflow clarity.
Suggestions
Add argument examples for non-trivial commands, e.g., `eightctl alarm create --time 07:00 --side left` and `eightctl schedule create --name 'weeknight' --start 22:00 --temp -5`
Include a verification pattern: after state-changing commands (temp, on/off, alarm create), suggest running `eightctl status` to confirm the change took effect
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. No unnecessary explanations—assumes Claude knows what Eight Sleep is, what CLI tools are, and how auth works. Every line earns its place. | 3 / 3 |
Actionability | Provides concrete CLI commands that are copy-paste ready, but lacks examples of full command usage with arguments (e.g., alarm create syntax, schedule create parameters, base angle values). Key details for non-trivial commands are missing. | 2 / 3 |
Workflow Clarity | The 'confirm before changing temperature or alarms' note is a good safety constraint, but there's no explicit workflow for multi-step operations like creating schedules or alarms. No validation/verification steps (e.g., checking status after changing temperature). | 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 is easy to scan. | 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
- deepgram/dglabs-deepclaw
- Commit
ec8d4f8
- 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.