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 ./openclaw/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 niche (Eight Sleep pods) with specific actions, making it distinctive. 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', '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 natural user-facing trigger terms such as 'smart bed', 'bed cooling', 'bed heating', 'mattress temperature', or 'sleep pod' to improve keyword 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/heating', or 'smart bed'. | 2 / 3 |
Distinctiveness Conflict Risk | 'Eight Sleep pods' is a very specific product/brand niche with distinct triggers. It is highly unlikely to conflict with other skills. | 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—parameterized commands like alarm create, schedule create, and base angle 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 verification steps.
Suggestions
Add argument syntax or brief examples for parameterized commands (e.g., `eightctl alarm create --time 07:00 --days mon,wed,fri`, `eightctl base angle 15`).
Include a verification step after state-changing commands (e.g., 'After setting temperature, run `eightctl status` to confirm the change took effect').
| 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 feedback loop described. Multi-step workflows (e.g., creating a schedule, verifying it was set) are absent. | 2 / 3 |
Progressive Disclosure | For a simple, short skill under 50 lines with no need for external references, the content is well-organized into clear sections (auth, quick start, common tasks, notes) that are 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
- trpc-group/trpc-agent-go
- Commit
0c1ec2b
- 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.