Home Assistant Manager skill

A Claude Code skill that edits and deploys Home Assistant configuration: YAML automations, validation, deploy and Lovelace dashboards

  • 982 ★ on the repository
  • Last commit
  • MIT
Skill

Extended access

Why this level

  • Runs commands over SSH and deploys changes to the Home Assistant instance
  • Can reload and restart the configuration of a live smart home
All reasons and checks

komal-skynet/claude-skill-homeassistant

Install

In your terminal, with SkillFoxx CLI

npx skillfoxx add skills/home-assistant-manager

Detects the agents on your machine, shows the access level and pins the version.

Other ways to install

Access and checks

How we review

Extended accessThe tool runs code or makes network calls and only reads external data.

  • Runs commands over SSH and deploys changes to the Home Assistant instance
  • Can reload and restart the configuration of a live smart home

This is third-party code. Review the repository files before installing.

What it does

The skill gives the agent a workflow for managing a remote Home Assistant instance. It edits YAML for automations, scripts, scenes and templates, validates the config with ha core check and delivers changes to the instance over git or a quick scp. It decides whether a reload is enough or a restart is needed, then confirms the result from logs, traces and entity state. A separate section covers building tablet-oriented Lovelace dashboards with Mushroom and Tile cards. For live state reads and service calls the skill prefers a Home Assistant MCP server when connected, and otherwise works over SSH and hass-cli.

Who it is for. For Home Assistant owners and devops engineers who keep their smart home config in git and edit it with an agent.

Good fit when

  • You need to write or fix an automation and verify it on a live instance
  • You need to build a Lovelace dashboard for a specific tablet
  • You need to apply config changes safely without unnecessary restarts

Not a fit when

  • You have no SSH access to the Home Assistant instance and no git set up in the /config directory
  • You only need to read state and call services, where a Home Assistant MCP server is enough

Example request

Create an automation that notifies me when the front door is open for more than five minutes, and verify it on the instance

Limitations

The skill assumes it edits the /config directory that is git-connected to the instance. It needs SSH access, hass-cli installed and HASS_SERVER and HASS_TOKEN in the environment, plus a git repository on the Home Assistant side. The ha core check validation takes tens of seconds. Documentation lookups via Context7 MCP are optional.

How to disable. Uninstall the home-assistant-manager plugin via /plugin or remove the skill folder from .claude/skills in the config directory.

FAQ

Does it replace a Home Assistant MCP server?

No, they complement each other. The MCP server gives live tools to read state and call services, while the skill defines the config editing procedure: deploy, reload-vs-restart choice and verification from logs.

What do I set up first?

SSH access to the instance, git in the /config directory, hass-cli installed and HASS_SERVER and HASS_TOKEN set in the shell environment.

Discussion

No questions or reviews yet.

Skills

Home Assistant best practices

Home Assistant Agent Skills

A skill of Home Assistant rules: native triggers instead of templates, safe renaming, dashboards and backups

SkillMinimal access973Repository stars

A Claude Code template: Home Assistant YAML automations, a custom React dashboard and checks before config is pushed.

WorkflowExtended access127Repository stars

Vibecode MCP lets Cursor, VS Code and Claude Code write Home Assistant automations and dashboards via an add-on agent

MCP serverBroad access58Repository stars

A skill collection by aahl: Home Assistant, Edge TTS and GLM-TTS speech, Qwen ASR, DuckDuckGo search, DeepWiki and Lark.

SkillExtended access165Repository stars

A Claude Code plugin and MCP server: the agent switches lights, locks doors and runs Apple HomeKit scenes from a Mac

PluginBroad access193Repository stars

A Node.js MCP server through which an agent controls Home Assistant devices and edits its automations

MCP serverBroad access574Repository stars

README in short

The README describes a skill that turns Claude Code into a Home Assistant assistant. It follows one canonical deploy flow: edit YAML, run ha core check, commit and push, git pull on the instance, reload or restart, then verify the result. It also covers modern automation syntax, modes and blueprints, and building tablet Lovelace dashboards. The repository is both a plugin and a self-hosted marketplace, installable via /plugin, by cloning into .claude/skills or by downloading an archive. MIT licensed.

README badge

Original SKILL.md

---
name: home-assistant-manager
description: Manage Home Assistant configuration safely and fast — edit and deploy YAML (automations, blueprints, scripts, scenes, templates, MQTT), validate with ha core check, deploy via git or rapid scp, reload-vs-restart correctly, verify changes from logs, traces and entity state, and build Lovelace dashboards. Use for any Home Assistant config, automation, template, or dashboard work over SSH/hass-cli/MCP.
---

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

Report a problem