How do I install the Homectl skill?

Run npx skillmds@latest add larsboes/homectl 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 Homectl 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 Homectl?

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 Homectl free to use?

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

Who published Homectl?

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

Homectl by larsboes — Agent Skill

Name: Homectl
Author: larsboes

Homectl

Materializes overlay-owned Home Assistant templates and vendors overlay-owned pinned components through a public, host-neutral CLI. Use for template coverage, materialization, or reviewed component vendoring. Real devices, automations, entity IDs, component selections, and output stay in the active private overlay.

larsboes 6af1b28 5 files · 33.6 KB Updated Sep 17, 2026

File contents

homectl

Operate the public materialization mechanism over a private Home Assistant definition. Axon owns the parser, validation, and vendoring behavior. The selected overlay owns the templates, variable map, component lockfile, helpers, and generated output.

Commands

scripts/homectl doctor
scripts/homectl materialize
scripts/homectl components [--only NAME] [--dry-run]

Defaults resolve from AXON_OVERLAY_ROOT, AXON_HOME_ROOT, or the overlay declared by axon.local.toml:

capability input: <overlay>/capabilities/home-assistant
variables: <overlay>/config/home-assistant.vars
generated output: <overlay>/build/home-assistant
component destination: <overlay>/config/home-assistant

Every path remains overridable for isolated tests.

Boundary

Never point generated output into public Axon.
Never place a real entity ID, hostname, component selection, or device name in this Pack.
Treat the set of templates and components as a private inventory even when their contents use placeholders and public Git references.
Review component diffs before replacement; runtime fetching is not allowed.

Read references/templating.md for the token contract and references/automation-doctrine.md for reusable reliability rules.

Frequently asked questions