How do I install the Ha Registry skill?

Run npx skillmds@latest add beclab/ha-registry in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Ha Registry safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Ha Registry?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Ha Registry free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Ha Registry?

beclab (@beclab) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Ha Registry by beclab — Agent Skill

Name: Ha Registry
Author: beclab

Ha Registry

Manage Home Assistant areas, devices, entities, floors, and labels with hass-cli. Use to list/create/rename/delete areas, assign devices or entities to areas, organize with floors and labels, rename entity_ids, or audit the registry. These are WebSocket-only operations (config/*_registry/*).

beclab 0da7972 2.6 KB Updated Sep 17, 2026

File contents

ha-registry

Organize the home: areas, devices, entities, floors, labels. Prerequisite: ../ha-shared/SKILL.md.

All registry operations are WebSocket-only. hass-cli routes them automatically; you do not pick the transport.

List

hass-cli registry area list
hass-cli registry device list
hass-cli registry entity list
hass-cli registry floor list
hass-cli registry label list

Mutate

create takes only --data (the new entry's fields). update and delete take the entry id as a positional argument — the CLI injects it as the correct <kind>_id key for you. Extra --data fields are merged in.

# Create an area (id is derived from the name by HA)
hass-cli registry area create --data '{"name":"Garage"}'

# Rename an area (positional id -> area_id)
hass-cli registry area update garage --data '{"name":"Garage Bay"}'

# Assign a device to an area
hass-cli registry device update <device_id> --data '{"area_id":"garage"}'

# Move an entity to an area / rename it
hass-cli registry entity update light.x --data '{"area_id":"garage","name":"Bay Light"}'

# Delete
hass-cli registry area delete garage

--data also accepts @file.json; on PowerShell prefer that over inline JSON (see ha-shared for the quoting note).

Categories (scoped)

Categories group items within a scope (e.g. automation, script, scene). Unlike the other registries, every call needs --scope:

hass-cli registry category list   --scope automation
hass-cli registry category create --scope automation --data '{"name":"Lighting"}'
hass-cli registry category update <category_id> --scope automation --data '{"name":"Lights","icon":"mdi:lightbulb"}'
hass-cli registry category delete <category_id> --scope automation

Assign an automation to a category by setting its categories via the entity registry: hass-cli registry entity update automation.x --data '{"categories":{"automation":"<category_id>"}}'.

Tips

Get ids first via the matching list. Names are not ids.
Entity/device area assignment: an entity inherits its device's area unless given its own area_id.
For fields you are unsure about, inspect the frontend behavior or use hass-cli raw ws config/entity_registry/get --data '{"entity_id":"..."}'.

---name: ha-registrydescription: Manage Home Assistant areas, devices, entities, floors, and labels with hass-cli. Use to list/create/rename/delete areas, assign devices or entities to areas, organize with floors and labels, rename entity_ids, or audit the registry. These are WebSocket-only operations (config/*_registry/*).---# ha-registryOrganize the home: areas, devices, entities, floors, labels. **Prerequisite:**[`../ha-shared/SKILL.md`](../ha-shared/SKILL.md).> All registry operations are WebSocket-only. hass-cli routes them> automatically; you do not pick the transport.## List```bashhass-cli registry area listhass-cli registry device listhass-cli registry entity listhass-cli registry floor listhass-cli registry label list```## Mutate`create` takes only `--data` (the new entry's fields). `update` and `delete`take the entry **id as a positional argument** — the CLI injects it as thecorrect `<kind>_id` key for you. Extra `--data` fields are merged in.```bash# Create an area (id is derived from the name by HA)hass-cli registry area create --data '{"name":"Garage"}'# Rename an area (positional id -> area_id)hass-cli registry area update garage --data '{"name":"Garage Bay"}'# Assign a device to an areahass-cli registry device update <device_id> --data '{"area_id":"garage"}'# Move an entity to an area / rename ithass-cli registry entity update light.x --data '{"area_id":"garage","name":"Bay Light"}'# Deletehass-cli registry area delete garage```> `--data` also accepts `@file.json`; on PowerShell prefer that over inline JSON> (see ha-shared for the quoting note).## Categories (scoped)Categories group items within a scope (e.g. `automation`, `script`, `scene`).Unlike the other registries, every call needs `--scope`:```bashhass-cli registry category list --scope automationhass-cli registry category create --scope automation --data '{"name":"Lighting"}'hass-cli registry category update <category_id> --scope automation --data '{"name":"Lights","icon":"mdi:lightbulb"}'hass-cli registry category delete <category_id> --scope automation```Assign an automation to a category by setting its `categories` via the entityregistry: `hass-cli registry entity update automation.x --data '{"categories":{"automation":"<category_id>"}}'`.## Tips- Get ids first via the matching `list`. Names are not ids.- Entity/device area assignment: an entity inherits its device's area unless given its own `area_id`.- For fields you are unsure about, inspect the frontend behavior or use `hass-cli raw ws config/entity_registry/get --data '{"entity_id":"..."}'`.

Frequently asked questions