Home Assistant Config Ops Agent Skill

Safely audit, validate, deploy, and troubleshoot a Home Assistant configuration across Kubernetes, SSH, or local runtimes.

Context cost
4.5k tokensestimated from the bundle, loaded when it triggers
Bundle
9 files · 19.1 kB1 script among them — read before you run
Licence
not declarednone named by its author
Last change
—no release on file
Servers it uses
Noneruns standalone

What it does

Safely audit, validate, deploy, and troubleshoot a Home Assistant configuration across Kubernetes, SSH, or local runtimes. Use for read-only HA health/configuration audits, creating or verifying repo-local .deployment_info metadata, checking repository-to-runtime drift, validating YAML or Pyscript changes, copying configuration, reading runtime logs and redacted automation/script traces, delivering approved Git revisions, restarting or verifying HA, and documenting repeatable operational methods.

What this skill changes about the agent has not been set out here as a list. Its SKILL.md, shown below, says it in the author’s own words.

devopskubernetes
Filed under

Cloud & DevOps

The skill itself

A skill is instructions the model reads, so you can see what you are getting: below is the start of its SKILL.md. The front matter loads with every session, the body loads when the skill triggers, and the whole file comes with the install.

SKILL.md4.0 kB · preview
--- name: home-assistant-config-ops ---
6# Home Assistant Config Ops
7
8Use a small repo-local .deployment_info file for instance-specific facts and
9this skill for reusable operational procedures. Treat the repository and the
10active HA runtime as separate evidence sources.
11
12## Establish scope and authority
13
141. Use the conversation's established facts, scope, and approvals. Read the
15 repository AGENTS.md, .deployment_info, and relevant local documentation
16 before runtime access. Ask only about missing or conflicting facts needed
17 for the next action.
182. If .deployment_info is missing or incomplete, follow
19 [deployment-bootstrap.md](references/deployment-bootstrap.md). Create it as
20 a separate preparatory step, not as part of a read-only audit.
213. Start runtime investigation read-only. Do not edit .storage, expose
22 secrets, call mutating services, copy files, restart HA, or deploy unless
23 the user explicitly authorizes that action.
244. Never commit, push, open a pull request, tag, deploy, or restart solely
This is a preview of SKILL.md. Download or install the skill to get the whole thing.
In the file
SKILL.md496 words
Files9
Licencenot declared
Why you can read it

Nothing in a skill executes. The client loads the text and the model follows it, so a skill can be audited the way a runbook is — by reading it.

What it costs in context

Skills are not billed by the call. They are paid for in context: every token the instructions occupy is a token your code, your diff and your conversation cannot use. Here is what this one takes and when it takes it.

≈170
always loaded
The name and description, so the model knows the skill exists and when to reach for it.
4,280
on trigger
The instruction body and 8 supporting files, read only when the skill fires.
2.2%
of a 200k window
Ten skills this size would take about 22% of the window before you open a file.
050k100k150k200k context window

4.5k tokens, estimated from the bundle at four bytes to the token, held for the rest of the session once it triggers. Heavy. Teams tend to install this one per project rather than globally, and load it only when the job comes up.

Servers bill, skills cost

A server charges by the month. A skill charges once per session, in context, and then keeps charging it for as long as the session lives.

Before and after

The same question, put to the same model twice: once as it comes, and once with these instructions loaded.

No worked example has been published for this skill yet.

The procedure it runs

The procedure has not been set out here step by step. It is in the body of its SKILL.md: the start of it is shown above, and the whole file comes with the install.

Prose, not code

These steps are written for a model to follow, not executed by a runtime. It can still be told to skip one, and it will say so when it does.

Servers it uses

None. This skill calls no MCP servers at all.

Everything it needs is in the instructions, so it works in a project with nothing connected — the model reads the file and changes how it works with what it can already reach.

Its SKILL.md does not declare which tools it asks the agent for, so what it touches is whatever the instructions themselves ask for — read them before you install it.

What it asks for
Writes filesnot declared
Network accessnot declared

This SKILL.md carries no allowed-tools line, so neither is declared. A skill grants no permissions of its own — it can only ask for tools your client already has.

What it will not do

Every skill is narrow, and the useful ones say where they stop. These are the jobs this one is the wrong tool for.

What this skill is not for has not been published here. Nothing is implied by that: it is a section the author has not filled in.

What is in the bundle

9 files, 19.1 kB on disk. Mostly text — the instructions the model reads — with 1 script in it that your client would run only if the instructions tell it to. 1 file of its source is not in the download — listed after these, with why.

  • SKILL.md4.0 kB
  • agents/openai.yaml0.3 kB
  • references/change-delivery.md2.3 kB
  • references/deployment-bootstrap.md2.1 kB
  • references/kubernetes.md2.9 kB
  • references/read-only-audit.md2.4 kB
  • references/runtime-traces.md2.5 kB
  • references/ssh-local.md1.3 kB
  • scripts/validate_pyscript_syntax.py1.3 kB

Not in the download

Not carried is a type a skill download does not hold. Take it from its source.

  • assets/deployment_info.templatenot carried
What is not in it

A skill installs nothing and depends on nothing: it is a folder your client reads. This one carries 1 script beside the text, so the download is 9 files — not the whole of its source: 1 file is left out. It is listed under the files, with why.

Install

Installing copies the bundle into your project. Nothing runs at install time — the files sit on disk until the model reads them.

# Home Assistant Config Ops · 4.5k tokens when loaded · macOS, Linux mkdir -p .claude/skills && t=$(mktemp -d) && curl -fsSL -o "$t/bundle.tar.gz" https://mcprush.com/api/skills/home-assistant-config-ops/bundle.tar.gz && tar -xzf "$t/bundle.tar.gz" -C "$t" && [ -d "$t/home-assistant-config-ops" ] && { [ ! -e .claude/skills/home-assistant-config-ops ] || { mv .claude/skills/home-assistant-config-ops "$t/.previous" && echo "Previous copy moved to $t/.previous"; }; } && mv "$t/home-assistant-config-ops" .claude/skills/ && echo "Installed .claude/skills/home-assistant-config-ops"
On Windows, or any OS with Node 20+
npx mcprush@latest skill add zewelor/home-assistant-config-ops

Windows PowerShell says 'running scripts is disabled on this system'? Run Set-ExecutionPolicy -Scope CurrentUser RemoteSigned once, or type npx.cmd instead of npx (codex.cmd, gemini.cmd, grok.cmd likewise). PowerShell 7 needs neither. Writes to .claude/skills/home-assistant-config-ops/ in the current project. For every project instead, run mkdir -p ~/.claude/skills && t=$(mktemp -d) && curl -fsSL -o "$t/bundle.tar.gz" https://mcprush.com/api/skills/home-assistant-config-ops/bundle.tar.gz && tar -xzf "$t/bundle.tar.gz" -C "$t" && [ -d "$t/home-assistant-config-ops" ] && { [ ! -e ~/.claude/skills/home-assistant-config-ops ] || { mv ~/.claude/skills/home-assistant-config-ops "$t/.previous" && echo "Previous copy moved to $t/.previous"; }; } && mv "$t/home-assistant-config-ops" ~/.claude/skills/ && echo "Installed ~/.claude/skills/home-assistant-config-ops" (macOS, Linux) — or add --global to the npx line. The curl line replaces .claude/skills/home-assistant-config-ops/ only after the download succeeds, so files left there by another skill of the same name, or by an older release, do not mix in. A copy already there is moved aside, not deleted, and the line prints where. Not in this download: 1 file of its source (which one, and why). Take it from its source.

Which clients pick it up on their own

A skill is a folder of text. Most of these read a skills folder and pick it up without being told; the rest take the same folder another way — an upload in the app, a parameter on an API call — and then choose it by its description just the same.

Claude Code.claude/skills/
Claude DesktopCustomize › Skills
ChatGPTSkills › Create › Upload
Cursor.cursor/skills/
VS Code.github/skills/
Codex CLI.agents/skills/
Gemini CLI.gemini/skills/
Grok Build.grok/skills/
Microsoft CopilotSkills › Upload a skill
PerplexityComputer › Skills › Upload a skill
DeepSeek Harness.dsh/skills/
Zed.agents/skills/
Devin Desktop.devin/skills/
Windsurf (legacy).windsurf/skills/
OpenAI Agents SDKInstructions or sandbox Skills
HTTP / APIa request parameter
This release
Versionnot versioned
Publishedno release date on file
PriceFree
Referencezewelor/home-assistant-config-ops

Versions

Its author publishes no version number, so there is nothing here to pin to: what you install is the folder as it stands today. Instructions change more often than APIs do — a skill can be rewritten entirely without anything it depends on moving.

Pinning

Nothing to pin to: this skill carries no version number of its own. What you install is what the folder holds on the day you install it.

Reviews

—no reviews yet

Nobody has reviewed this skill yet. The rating is the mean of the reviews written here, so there is none until somebody writes the first.

Sign in to review it

A review is tied to an account so it can be answered, edited and taken down by the person who wrote it.

Sign in
Who can post

Anybody with an account, one review each. It carries the version that was current when you wrote it, and the publisher may reply once.

Publisher
Servers0
Claim this skill