
Eightctl
Let your coding agent drive Eight Sleep pod status, temperature, alarms, schedules, and audio through the eightctl CLI.
Overview
eightctl is an agent skill for the Build phase that controls Eight Sleep pods via the eightctl CLI (status, temperature, alarms, schedules, audio, base).
Install
npx skills add https://github.com/steipete/clawdis --skill eightctlWhat is this skill?
- Status and power: eightctl status, on, off
- Temperature control with explicit confirm-before-change guidance
- Alarms: list, create, dismiss
- Schedules: list, create, update
- Audio and adjustable base: state, play, pause, angle commands
- Documented command families: status/power, temperature, alarms, schedules, audio, and base angle
- Requires eightctl binary via documented Go module install path
Adoption & trust: 1.8k installs on skills.sh; 378k GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You want your agent to adjust your Eight Sleep pod without manually switching apps or guessing undocumented API calls.
Who is it for?
Eight Sleep owners who already use agentic coding workflows and want scripted, confirmable pod control from the terminal.
Skip if: Anyone without an Eight Sleep pod, or teams needing supported enterprise APIs with SLA-backed device management.
When should I use this skill?
User asks to control Eight Sleep pod status, temperature, alarms, schedules, audio, or base via eightctl.
What do I get? / Deliverables
The agent runs documented eightctl commands for status, comfort, and schedules after auth is configured, with guardrails on rate limits and destructive changes.
- Executed eightctl commands with user confirmation on sensitive changes
- Pod status and configuration readouts from CLI output
Recommended Skills
Journey fit
Device control via a local CLI is an integration you wire into your agent toolchain during build, not a launch or growth task. Matches build/integrations where personal hardware APIs are scripted and authenticated from the dev environment.
How it compares
A thin CLI integration skill, not a general smart-home MCP server or official vendor SDK.
Common Questions / FAQ
Who is eightctl for?
Solo builders with Eight Sleep hardware who use coding agents and want pod commands from eightctl instead of manual app clicks.
When should I use eightctl?
During Build when wiring personal device integrations—e.g. check pod status, set temperature before sleep, or list alarms from an agent session.
Is eightctl safe to install?
Check the Security Audits panel on this page; store credentials in config or env vars you control, and expect an unofficial, rate-limited API.
SKILL.md
READMESKILL.md - Eightctl
# eightctl Use `eightctl` for Eight Sleep pod control. Requires auth. Auth - Config: `~/.config/eightctl/config.yaml` - Env: `EIGHTCTL_EMAIL`, `EIGHTCTL_PASSWORD` Quick start - `eightctl status` - `eightctl on|off` - `eightctl temp 20` Common tasks - Alarms: `eightctl alarm list|create|dismiss` - Schedules: `eightctl schedule list|create|update` - Audio: `eightctl audio state|play|pause` - Base: `eightctl base info|angle` Notes - API is unofficial and rate-limited; avoid repeated logins. - Confirm before changing temperature or alarms.