Installs into .claude/skills of the current project.
Are you the author of Ha Boot?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/gtapps-ha-boot-hermitd)
---
name: ha-boot
description: Check Home Assistant connectivity, context freshness, and locale. Auto-refresh context if stale. Use at session start or when HA status is unclear.
allowed-tools:
- Bash
- Read
- Glob
- mcp__homeassistant__GetLiveContext
- mcp__homeassistant__GetDateTime
---
# HA Boot Check
Run this at the start of every session or when you need to verify HA status.
This skill is the single entry point for this project — it also initializes the hermit session.
## Steps
0. **Resident startup**: Invoke the `/hermitd:resident-start` skill first to establish readiness before HA work begins. If it errors (e.g. core hermit not initialized), stop and tell the operator to run `/hermitd-homeassistant:hatch`.
1. Run `${CLAUDE_PLUGIN_ROOT}/bin/ha-agent-lab boot status --probe` and present the result.
2. Read `.hermit/OPERATOR.md` for the stored language (in the `## HA hermit` section). All user-facing output should use this locale.
3. Check `.hermit/raw/snapshot-ha-normalized-latest.json` modification time.
- If older than 24 hours or missing, auto-run `${CLAUDE_PLUGIN_ROOT}/bin/ha-agent-lab ha refresh-context`.
4. Optionally call `GetLiveContext` via MCP for a quick live snapshot.
5. Present a summary:
- HA connectivity: ok/failed
- Context: fresh/stale/missing (age in hours)
- Language: the stored locale
- Entity count from last context
## If Something Is Missing
- No `.env` or missing token: tell the operator to create `.env` at the project root and set `HOMEASSISTANT_TOKEN`.
- No endpoint: tell the operator to set `HOMEASSISTANT_URL` in `.env`.
- No language in OPERATOR.md: ask the operator for their preferred locale.
