Menu
Home Assistant: energy, temperature, cameras, alarms, devices, sensors, automations.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use for any Microsoft account, personal or work (Outlook.com, Hotmail, Live, Microsoft 365); preferred over email-client for Microsoft accounts. Graph-based mail (read/send/reply/forward, drafts, flag/categorize, move/archive, folders, attachments, block senders), calendar and meetings, Microsoft Teams (chats, channels, presence), and new-mail/Teams notifications. Requires daemon.
Browse, navigate, click, fill forms, screenshot, or scrape web pages with a stealth (Camoufox) browser.
Design judgment and UI copy for building Vesta dashboard widgets that feel considered rather than templated, within the fixed design system.
Use before building or modifying the user's dashboard: widgets, pages, layouts, custom UI. Understand what the user wants, design it, write a spec, then dispatch the dashboard-builder to build it.
Use when someone who doesn't have their own vesta asks what vesta is, how to get one, or hints they want in. Vesta is invite-only: you gatekeep and build desire through scarcity, draw out what they want, then sell vesta as indispensable to their goals and set them up end-to-end in chat. Not for the owner, who already has one.
Talk to vestad, the host daemon that runs this container. Register a background service to get a port, build public URLs, update vestad to the latest release, check its version, and read gateway logs. Use when a skill needs an inbound port or a shareable link, when the user asks to update Vesta, or when debugging gateway/container issues.
| name | home-assistant |
| description | Home Assistant: energy, temperature, cameras, alarms, devices, sensors, automations. |
ha state sensor.temperature # get entity state (compact); --full for all attributes
ha states --domain sensor # list entities by domain
ha states --search kitchen # search entities by name
ha history sensor.power --hours 6 # state history (default 24h)
ha weather # condition, temperature, humidity, wind, sunrise/sunset
ha service switch turn_on --entity-id switch.my_switch # call any HA service
ha service light turn_on --entity-id light.desk --data '{"brightness": 128}' # with JSON payload
ha ping # verify API connectivity
Discover entities with ha states --domain <domain> or --search <query>; common domains: sensor, binary_sensor, switch, light, climate, alarm_control_panel, person, weather, camera, todo. Once you know the entity IDs, read with ha state and control with ha service.
# Requires environment variables:
# HASS_TOKEN - long-lived access token from HA
# HASS_URL - HA base URL (default: http://homeassistant.local:8123)
source /etc/environment
uv tool install --editable ~/agent/skills/home-assistant/cli