Home Assistant Manager

This is the real deal for managing Home Assistant remotely, not just basic config editing. You get complete workflows for SSH and hass-cli access, smart deployment strategies (git for final changes, scp for rapid iteration), and actual verification protocols so you know your automations work before they fail at 3am. The reload versus restart guidance alone saves time, and the Lovelace dashboard section covers tablet-optimized UIs with concrete deployment patterns. It's opinionated about process, which is exactly what you need when you're managing a production home automation system from your laptop instead of clicking through the web UI.

skills.sh installs: 261
GitHub stars: 982
last updated: Jun 3, 2026

View on GitHub

Install

$ npx -y skills add komal-skynet/claude-skill-homeassistant --skill home-assistant-manager --agent claude-code

Installs into .claude/skills of the current project.

Files

dashboard.png

Home Assistant Manager

Operate a remote Home Assistant instance precisely: make a change, get it live, prove it worked. Optimize for the fewest safe round-trips.

Assumptions

The repo you're editing is the HA /config dir, git-connected to the instance. Edits aren't live until pulled on the instance.
root@homeassistant.local in examples is a placeholder. Resolve the real user/host once (project CLAUDE.md, ~/.ssh/config, or ask) and if it isn't recorded in the project CLAUDE.md yet, add it so future sessions skip this step.
Access via one or more of: hass-cli (REST), SSH ha, or an MCP server (see below).
Only edit .yaml/.yml/.md. Never read/write .env or secrets.yaml; use !secret.