eightctl
Control Eight Sleep pods (status, temperature, alarms, schedules).
66
61%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
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 completely lacks a 'Use when...' clause, which is critical for Claude to know when to select this skill from a large pool. Adding natural user trigger terms and explicit usage guidance would significantly improve it.
Suggestions
Add a 'Use when...' clause, e.g., 'Use when the user asks about their Eight Sleep pod, smart bed, bed temperature, sleep schedule, or bed alarms.'
Include common user-facing synonyms like 'smart bed', 'bed cooling/heating', 'mattress temperature', '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 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 covers the basics of the eightctl CLI. Its main weakness is incomplete actionability—parameterized commands like alarm creation and schedule management lack argument syntax or examples, which would leave Claude guessing at the correct invocation. The safety notes are present but could be more specific about confirmation workflows.
Suggestions
Add argument syntax or examples for parameterized commands (e.g., `eightctl alarm create --time 07:00 --days mon,wed,fri`, `eightctl temp <-10 to 10>`) to make them fully actionable.
Specify a brief confirmation workflow for destructive/state-changing operations (e.g., 'Before changing temperature or alarms, show current state with `eightctl status` and confirm with the user').
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. Every line serves a purpose—no explanation 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 more complex usage (e.g., `eightctl alarm create` arguments, `eightctl schedule create` syntax, `eightctl temp` range). Key details for parameterized commands are missing. | 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—there's no explicit validation or confirmation workflow. Multi-step processes like creating schedules or alarms have no sequenced steps. | 2 / 3 |
Progressive Disclosure | For a simple, short skill under 50 lines with no need for external references, the content is well-organized into logical sections (auth, quick start, common tasks, notes) with clear navigation. | 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
- qsimeon/openclaw-engaging
- Commit
4467e04
- 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.