메뉴
Fetch local Home Assistant config snapshots from ha-data/ via fetch-ha-data.sh, gated by a freshness check. Use when a request touches existing automations, scenes, scripts, configuration.yaml, or Core/Supervisor logs — none of which the MCP server exposes.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
ESPHome device YAML authoring and esphome.io documentation navigation. Use when a request touches ESPHome firmware, device configuration, components (sensors, binary sensors, switches, lights, GPIO, I2C, SPI, UART, BLE, OTA, native API, MQTT), automations, lambdas, substitutions, packages, external components, or HA integration of ESPHome devices. Provides a structured sitemap of esphome.io so the agent fetches the correct page directly instead of crawling, plus practical working guidance for device YAML structure.
Output contract for Home Assistant implementation requests — the YAML / How This Works / Customization Ideas structure, runnable output only to .temp/, minimal valid YAML. Use when creating or editing automations, scripts, scenes, blueprints, or configuration.
Present Home Assistant live entity states with domain emojis, grouped by area or function. Use when answering current states, status checks, or monitoring queries from GetLiveContext output.
Docs-backed Home Assistant troubleshooting playbook — config check, logs, traces, Developer Tools, debug logging. Use when an automation, integration, or entity is failing, erroring, or misbehaving.
Structured sitemap of the official Home Assistant documentation (home-assistant.io/docs/) and the Companion App documentation (companion.home-assistant.io/docs/). Provides direct links to every major section and sub-page so agents can navigate to the correct docs page without crawling. Use when an agent needs to find the right HA documentation URL for automations, scripts, scenes, blueprints, templates, configuration, integrations, dashboards, energy, voice assistants, companion app notifications, sensors, location tracking, or troubleshooting.
Benchmark multiple AI model outputs from the ha-release-notes prompt against ground truth built from the user's live HA setup. Discovers model results, builds a release-specific scoring spec, evaluates each model on 7 weighted dimensions, and writes a ranked comparison. Use when user wants to compare, evaluate, score, or benchmark release note summaries from different models, or says "benchmark", "compare models", "score the results".
| name | ha-config-fetch |
| description | Fetch local Home Assistant config snapshots from ha-data/ via fetch-ha-data.sh, gated by a freshness check. Use when a request touches existing automations, scenes, scripts, configuration.yaml, or Core/Supervisor logs — none of which the MCP server exposes. |
configuration.yaml, or logs.ha-data/ snapshots are the only source.Before reading any file from ha-data/, run:
find ha-data/ -name '*.yaml' -mmin +1440 -print -quit | grep -q . && echo STALE || echo FRESH
./fetch-ha-data.sh from this skill's folder.Debugging requests (troubleshooting, log analysis, error investigation) always re-fetch — logs and state change frequently.
If ha-data/ does not exist at all, treat it as stale.
Run from the repository root:
.github/skills/ha-config-fetch/fetch-ha-data.sh
Optional: override the config directory (default /config):
.github/skills/ha-config-fetch/fetch-ha-data.sh /custom/path
After the script completes, read the file(s) you need:
ha-data/automations.yaml — all automationsha-data/scenes.yaml — all scenesha-data/scripts.yaml — all scriptsha-data/configuration.yaml — main configurationha-data/customize.yaml — entity customizationsha-data/esphome/*.yaml — every ESPHome device YAML found under the ESPHome data dir (secrets.yaml is always skipped, never snapshotted)ha-data/zigbee2mqtt/configuration.yaml — Zigbee2MQTT main configha-data/zigbee2mqtt/devices.yaml — Zigbee2MQTT device definitionsha-data/zigbee2mqtt/groups.yaml — Zigbee2MQTT groupsha-data/zigbee2mqtt/state.json — Zigbee2MQTT runtime state (not YAML; freshness gate does not cover it — debugging requests always re-fetch)ha-data/logs/core.log — latest HA Core container logs (debugging)ha-data/logs/supervisor.log — latest Supervisor container logs (debugging)ha-data/ — gitignored, local-only snapshots.