eightctl

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

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./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.

A lean, command-dense body that respects the context window and covers all major command groups with sensible operational cautions. The only real gap is missing argument syntax for the create/update subcommands and the absence of an auth-setup/verification step.

Dimension	Reasoning	Score
Conciseness	The ~25-line body is lean and entirely factual ("eightctl temp 20", "API is unofficial and rate-limited; avoid repeated logins") with zero padding or explanation of concepts Claude already knows, matching anchor 5's 'every token earns its place'.	5 / 5
Actionability	Commands are concrete and copy-paste ready ("eightctl status", "eightctl alarm list\|create\|dismiss"), but "alarm create" and "schedule update" are listed without argument syntax, leaving minor gaps that keep it below anchor 5's fully-executable bar.	4 / 5
Workflow Clarity	Each single action is unambiguous and "Confirm before changing temperature or alarms" provides a checkpoint, but there is no auth-verification step or error-recovery guidance (e.g., what to do on login failure), matching anchor 4's 'clear sequence with most checkpoints; minor validation gaps'.	4 / 5
Progressive Disclosure	The skill is under 50 lines, needs no external references (none exist in the bundle and none are referenced), and is organized into clear sections (Auth, Quick start, Common tasks, Notes), which the guidelines say merits a 5 for simple skills.	5 / 5
	Total	18 / 20 Passed

Description

62%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, specific, and highly distinctive thanks to naming the Eight Sleep product, but it completely lacks a 'when to use' clause and misses natural trigger synonyms like 'bed' or 'mattress'. Adding an explicit usage trigger would raise completeness and trigger-term quality substantially.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user mentions Eight Sleep, their smart mattress, or asks to check or change bed temperature, alarms, or sleep schedules."

Include natural synonyms users would actually say — "bed", "mattress", "warm/cool the bed", "wake-up alarm" — to improve trigger term coverage.

Consider mentioning audio/base control if those are common requests, since the body supports them but the description omits them.

Dimension	Reasoning	Score
Specificity	"Control Eight Sleep pods (status, temperature, alarms, schedules)" names the domain plus four concrete capability areas, matching anchor 4's 'several specific actions; minor gaps' — audio and base commands from the body are omitted, so coverage is not comprehensive enough for 5.	4 / 5
Completeness	The 'what' is clear (status, temperature, alarms, schedules control), but there is no 'Use when...' clause or equivalent trigger guidance, which the judging guidelines explicitly cap at 3.	3 / 5
Trigger Term Quality	"Eight Sleep", "pods", "temperature", "alarms", and "schedules" are relevant keywords, but common natural phrasings users would say ("bed", "mattress", "warm/cool the bed", "wake-up") are missing, matching anchor 3's 'missing common variations or synonyms'.	3 / 5
Distinctiveness Conflict Risk	"Eight Sleep pods" names a specific product with a clear niche and distinct triggers, so it is unlikely to fire for unrelated skills, matching anchor 5's 'clear niche with distinct triggers; minimal conflict risk'.	5 / 5
	Total	15 / 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: Bitterbot-AI/bitterbot-desktop
Path: skills/eightctl/SKILL.md
Commit: 1c7dc1b

Reviewed: 19 hours 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.