eightctl

Control Eight Sleep pods (status, temperature, alarms, schedules).

2.07x

Quality

78%

Does it follow best practices?

Impact

83%

2.07x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./openclaw/skills/eightctl/SKILL.md

The canonical home for this skill is eightctl in openclaw/openclaw

Quality

Content

86%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is a lean, well-structured command reference with executable commands and a useful safety checkpoint. Expanding a few shorthand command groups with concrete example arguments would make it fully copy-paste-ready.

Suggestions

Add example arguments to shorthand command groups, e.g. `eightctl alarm create --time 07:00` and `eightctl schedule update --bedtime 22:30`, to reach fully copy-paste-ready guidance.

Add a brief auth-readiness check (e.g. verify `~/.config/eightctl/config.yaml` exists or env vars are set) as a validation step before running commands.

Show one short end-to-end example sequence (status → set temp → confirm) to make the implicit workflow explicit.

Dimension	Reasoning	Score
Conciseness	The body is lean and token-efficient—just config paths, env vars, and terse command lists with no concept over-explanation—matching the 'lean and efficient; every token earns its place' anchor.	5 / 5
Actionability	It lists concrete, executable commands covering common cases (e.g., `eightctl status`, `eightctl temp 20`), but several entries use union shorthand (`alarm list\|create\|dismiss`) without example arguments, leaving minor gaps versus fully copy-paste-ready examples.	4 / 5
Workflow Clarity	As a simple single-purpose skill it has a clear Quick start/Common tasks structure plus an explicit 'Confirm before changing temperature or alarms' checkpoint, but there is no full multi-step sequence with feedback loops, so it sits at 4 rather than 5.	4 / 5
Progressive Disclosure	The body is under 50 lines with no need for external references (no bundle files present) and is well-organized into Auth, Quick start, Common tasks, and Notes sections, satisfying the simple-skill exception for a 5.	5 / 5
	Total	18 / 20 Passed

Description

70%Weight 40%Scale 1-5

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 specific with a clear niche, but lacks any explicit 'Use when...' trigger guidance, capping completeness. Adding a trigger clause referencing Eight Sleep, smart bed, or pod temperature/alarm requests would lift it.

Suggestions

Append an explicit trigger clause such as 'Use when controlling an Eight Sleep pod or when the user mentions Eight Sleep, smart-bed temperature, or bed alarms/schedules.'

Add a couple of natural synonyms (e.g., 'bed', 'mattress') to broaden trigger-term coverage.

Rephrase capability nouns as verb-actions (e.g., 'Set temperature, manage alarms and schedules, check status') for sharper specificity.

Dimension	Reasoning	Score
Specificity	The phrase 'Control Eight Sleep pods (status, temperature, alarms, schedules)' names the domain plus four concrete capability areas, matching the 'several specific actions; minor gaps' anchor; it falls short of 5 because the actions are noun-categories rather than verb-actions and lack full coverage of subcommands.	4 / 5
Completeness	There is a clear 'what' (control pods and their status/temperature/alarms/schedules) but no 'Use when...' or equivalent trigger clause, so per the judging guidelines completeness is capped at 3.	3 / 5
Trigger Term Quality	Natural terms a user would say ('status', 'temperature', 'alarms', 'schedules', 'Eight Sleep pods') are present, but common synonyms (bed, mattress, sleep) are missing, fitting the 'good coverage; a few natural terms missing' anchor rather than 5.	4 / 5
Distinctiveness Conflict Risk	'Eight Sleep pods' is a specific, niche smart-bed device with distinct triggers and minimal overlap with other skills, matching the 'clear niche with distinct triggers; minimal conflict risk' anchor.	5 / 5
	Total	16 / 20 Passed

Validation

81%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 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	13 / 16 Passed

Repository: trpc-group/trpc-agent-go
Path: openclaw/skills/eightctl/SKILL.md
Commit: ba4a78e

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.