mcpbeat Sign in

Hass Builder Skill for Claude

by aahl

A skill to build and manage Home Assistant configurations. Use when using the Home Assistant Builder (`hab`) CLI to inspect, create, update, delete, operate, or troubleshoot Home Assistant resources; when a user mentions hab, Home Assistant CLI automation, Lovelace/dashboard edits, helpers, automations, scripts, backups, ESPHome, or Home Assistant operations from a terminal.

2k tokens
context cost
the whole folder, loaded on every use
2
files
ships runnable scripts
0
copies elsewhere
how many repositories repackaged it
147
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/aahl/skills --skill hass-builder

The instruction itself

8 sections, as written by the author

Home Assistant Builder (hab)

A CLI utility designed for LLMs to build and manage Home Assistant configurations.

Start Every Workflow

The script scripts/hab.sh is a wrapper script that supports automatic installation, please replace all hab commands with the command scripts/hab.sh.

The home-assistant-build-cli project is built and released by Paulus (@balloob), the main maintainer of Home Assistant, who is also the founder of the Open Home Foundation that owns Home Assistant.

alias hab='scripts/hab.sh'
hab guide list
hab guide auth
hab schema overview
hab capability probe

Then read the topic and command schema for the specific workflow:

| Task | First commands |

| --- | --- |

| Discovery / inventory | hab guide discovery; hab schema entity list |

| Automation / script / scene | hab guide automation; hab schema automation create --json |

| Dashboard / Lovelace | hab guide dashboard; hab schema dashboard card create --json |

| Helpers | hab guide helpers; hab helper types --json |

| Calendar / to-do | hab guide calendar-todo |

| Backups / system / network | hab guide operations; hab schema system restart |

| ESPHome | hab guide esphome; hab schema esphome validate --json |

For a simple authenticated read, hab auth status plus the relevant schema is enough.

Output and Parsing

Use --json whenever Claude or another program will parse output. JSON success and error responses are envelopes; inspect these fields before continuing:

  • success
  • data
  • error.code, error.details.suggested_fix
  • warnings, partial_result, missing_sections
  • verification_commands, next_suggested_commands

ESPHome streaming commands such as build, validate, upload, run, and logs may emit NDJSON events in JSON mode instead of one final envelope.

Mutations and Risk Gates

Inspect before changing state:

  • Read the guide/schema for the command.
  • Gather current state with read-only list/get commands.
  • Preview the mutation with --plan or --dry-run when supported.
  • Show the preview and ask the user before executing risky operations.
  • Run verification commands from the plan or a follow-up get/list command.

Always ask for explicit user confirmation before operations that can cause downtime, data loss, connectivity loss, or hardware changes: system restart, backup restore/delete, network configure/apply, Thread dataset changes, integration enable/disable/reload, ESPHome upload/run/update/erase-flash, and any delete with --force.

Do not add --force just to make a command non-interactive. Use it only after the user has approved the exact operation.

Input Payloads

Commands that accept data usually support:

| Method | Use when | Pattern |

| --- | --- | --- |

| --data / -d | Short JSON payloads | hab automation create id -d '{...}' --json |

| --file / -f | Larger YAML/JSON payloads | hab automation update id -f automation.yaml |

| stdin heredoc | Multi-line payload without temp file | hab automation create id <<'EOF' |

Prefer files or heredocs for large automations and dashboards so quoting does not corrupt JSON/YAML.

Common Command Patterns

# Authentication and instance checks
hab auth status
hab overview
hab capability probe

# Entity inventory
hab entity list --domain light
hab entity get light.kitchen --device --related
hab search related entity light.kitchen

# Safe mutation preview
hab schema area create --json
hab area create "Kitchen" --plan
hab area create "Kitchen"

# Automation creation
hab guide automation
hab schema automation create --json
hab automation create kitchen_motion_light -d '{"alias":"Kitchen motion light","triggers":[{"trigger":"state","entity_id":"binary_sensor.kitchen_motion","to":"on"}],"conditions":[],"actions":[{"action":"light.turn_on","target":{"entity_id":"light.kitchen"}}]}' --dry-run

# Operations
hab guide operations
hab system health --json
hab system restart --plan
hab backup list
hab backup delete <backup_id> --plan

Response Pattern

When answering a user asking for hab commands:

  • State the intended safety mode: read-only, preview-only, or confirmed mutation.
  • Provide commands in execution order.
  • Mark any command that requires user confirmation.
  • Say what JSON fields to inspect before the next step.
  • Include verification commands.

Common Mistakes

| Mistake | Better approach |

| --- | --- |

| Guessing command flags from memory | Run hab schema <command> --json first |

| Parsing text output | Use --json and inspect envelope fields |

| Creating resources without inventory | list/get/search related first |

| Skipping mutation preview | Use --plan or --dry-run when supported |

| Using --force for convenience | Confirm the exact risky operation first |

| Treating ESPHome JSON as one object | Handle NDJSON stream events for streaming commands |

| Ignoring verification_commands | Run them or explain why not |

Other skills for the same job

different authors, same section of the catalogue
D3 Viz
by chrisvoncsefalvay
×3

Creating interactive data visualisations using d3.js. This skill should be used when creating custom charts, graphs, network diagrams, geographic visualisations, or any complex SVG-based data visualisation that requires fine-grained control over visual elements, transitions, or interactions. Use this for bespoke visualisations beyond standard charting libraries, whether in React, Vue, Svelte, vanilla JavaScript, or any other environment.

20k tokens
Astropy
by christophacham
×3

Comprehensive Python library for astronomy and astrophysics. This skill should be used when working with astronomical data including celestial coordinates, physical units, FITS files, cosmological calculations, time systems, tables, world coordinate systems (WCS), and astronomical data analysis. Use when tasks involve coordinate transformations, unit conversions, FITS file manipulation, cosmological distance calculations, time scale conversions, or astronomical data processing.

16k tokens
Instrument Data To Allotrope
by anthropics
vendor ×2

Convert laboratory instrument output files (PDF, CSV, Excel, TXT) to Allotrope Simple Model (ASM) JSON format or flattened 2D CSV. Use this skill when scientists need to standardize instrument data for LIMS systems, data lakes, or downstream analysis. Supports auto-detection of instrument types. Outputs include full ASM JSON, flattened CSV for easy import, and exportable Python code for data engineers. Common triggers include converting instrument files, standardizing lab data, preparing data for upload to LIMS/ELN systems, or generating parser code for production pipelines.

33k tokens scripts
Qutip
by ComeOnOliver
×2

Quantum mechanics simulations and analysis using QuTiP (Quantum Toolbox in Python). Use when working with quantum systems including: (1) quantum states (kets, bras, density matrices), (2) quantum operators and gates, (3) time evolution and dynamics (Schrödinger, master equations, Monte Carlo), (4) open quantum systems with dissipation, (5) quantum measurements and entanglement, (6) visualization (Bloch sphere, Wigner functions), (7) steady states and correlation functions, or (8) advanced methods (Floquet theory, HEOM, stochastic solvers). Handles both closed and open quantum systems across various domains including quantum optics, quantum computing, and condensed matter physics.

27k tokens
Copilot Usage Metrics
by github
vendor ×1

Retrieve and display GitHub Copilot usage metrics for organizations and enterprises using the GitHub CLI and REST API.

1k tokens scripts
Mentoring Juniors
by github
vendor ×1

Socratic mentoring for junior developers and AI newcomers. Guides through questions, never answers. Triggers: "help me understand", "explain this code", "I''m stuck", "Im stuck", "I''m confused", "Im confused", "I don''t understand", "I dont understand", "can you teach me", "teach me", "mentor me", "guide me", "what does this error mean", "why doesn''t this work", "why does not this work", "I''m a beginner", "Im a beginner", "I''m learning", "Im learning", "I''m new to this", "Im new to this", "walk me through", "how does this work", "what''s wrong with my code", "what''s wrong", "can you break this down", "ELI5", "step by step", "where do I start", "what am I missing", "newbie here", "junior dev", "first time using", "how do I", "what is", "is this right", "not sure", "need help", "struggling", "show me", "help me debug", "best practice", "too complex", "overwhelmed", "lost", "debug this", "/socratic", "/hint", "/concept", "/pseudocode". Progressive clue systems, teaching techniques, and success metrics.

4k tokens
Astropy
by K-Dense-AI
×1

Core Python library for astronomy and astrophysics workflows that need Astropy APIs, including units/quantities, coordinates, FITS I/O, tables, time systems, WCS, and cosmology. Use when implementing or debugging astronomical data analysis code with Astropy.

18k tokens
Polars
by K-Dense-AI
×1

High-performance DataFrame library for Python ETL, analytics, and pandas migration. Use for expression-based data manipulation with lazy query optimization, parallel execution, streaming out-of-core processing, Arrow interoperability, and optional GPU execution.

20k tokens

How to use it

Copy the folder

Take aahl/hass-builder from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.