CtrlK
BlogDocsLog inGet started
Tessl Logo

eightctl

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

69

2.07x
Quality

61%

Does it follow best practices?

Impact

83%

2.07x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/eightctl/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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—while simple commands are clear, more complex operations (alarm create, schedule create) lack argument syntax or examples. Adding a verification step after state-changing operations would improve workflow clarity.

Suggestions

Add argument syntax examples for complex commands like `eightctl alarm create <time> <days>` and `eightctl schedule create` with sample parameters.

Include a verification workflow: after changing temperature or alarms, suggest running `eightctl status` to confirm the change took effect.

DimensionReasoningScore

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 command 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 checkpoint, but there's no explicit workflow for multi-step tasks like creating schedules or alarms. No validation/feedback loop for confirming changes took effect (e.g., checking status after setting temp).

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 easy to navigate.

3 / 3

Total

10

/

12

Passed

Description

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 lacks a 'Use when...' clause, which significantly hurts completeness and could make it harder for Claude to know when to select this skill. Adding common user trigger terms and explicit usage guidance would improve it substantially.

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 additional natural trigger terms users might say, such as 'bed cooling', 'bed heating', 'smart mattress', 'sleep temperature', or 'bed warmth'.

DimensionReasoningScore

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 (control Eight Sleep pods) but has no explicit 'Use when...' clause or equivalent 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' and 'pods' as natural keywords, plus action terms like 'temperature', 'alarms', 'schedules'. However, it misses common user variations like 'bed temperature', 'sleep tracking', 'smart mattress', or 'bed cooling/heating'.

2 / 3

Distinctiveness Conflict Risk

'Eight Sleep pods' is a very specific product niche. This is unlikely to conflict with any other skill due to the highly specific hardware/brand reference.

3 / 3

Total

9

/

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.

Validation8 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

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
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.