/ha-delete-config
Delete an automation or script from Home Assistant via REST API with operator confirmation. Use when the operator asks to remove, delete, or disable a specific automation or script.
Claude Code
$ npx -y skills add gtapps/hermitd --skill ha-delete-config --agent claude-code
Codex
$ npx skills add gtapps/hermitd --skill ha-delete-config -a codex -y
Cursor
$ npx skills add gtapps/hermitd --skill ha-delete-config -a cursor -y
Gemini CLI
$ npx skills add gtapps/hermitd --skill ha-delete-config -a gemini-cli -y
GitHub Copilot
$ npx skills add gtapps/hermitd --skill ha-delete-config -a github-copilot -y
OpenCode
$ npx skills add gtapps/hermitd --skill ha-delete-config -a opencode -y
Windsurf
$ npx skills add gtapps/hermitd --skill ha-delete-config -a windsurf -y
SKILL.md
ha-delete-config.SKILL.mdname: ha-delete-config
description: Delete an automation or script from Home Assistant via REST API with operator confirmation. Use when the operator asks to remove, delete, or disable a specific automation or script.
allowed-tools:
- Bash
- Read
Delete HA Config
Removes an automation or script from Home Assistant via `DELETE /api/config/{domain}/config/{id}`.
Steps
1. **Identify the target**: Ask the operator which automation or script to delete (name or ID).
- If unknown, list options: `${CLAUDE_PLUGIN_ROOT}/bin/ha-agent-lab ha list-automations` or `ha list-scripts`.
- Each entry under `automations` (or `scripts`) carries `id`, the config ID needed for deletion. `friendly_name` shows the UI display name (this is HA's `friendly_name` attribute, which may differ from the YAML `alias:` field if the operator customized it via the UI).
- `deletable` is `false` for YAML-packaged automations (no numeric `id`): these cannot be removed via REST. Tell the operator to delete the YAML block from their config files and reload manually instead.
2. **Preview**: Show the target details (entity_id, id, friendly_name, state). This action cannot be undone via CLI.
3. **Delete**: Run the appropriate command:
- `${CLAUDE_PLUGIN_ROOT}/bin/ha-agent-lab ha delete-automation <id>` for automations.
- `${CLAUDE_PLUGIN_ROOT}/bin/ha-agent-lab ha delete-script <id>` for scripts.
4. **Check result**:
- `OK`: config deleted. The entity stays in the registry until the next reload.
- `{"status":"not_found","reason":"no_config"}`: the ID doesn't exist in HA.
- `{"error":...}`: surface the error to the operator.
5. **Reload (optional)**: After deletion the entity stays in the registry until the next reload. Offer to trigger one:
- Tell the operator to go to **HA Developer Tools → Services → `automation.reload`** (or `script.reload`).
- Do **not** use `validate-apply` for this — it would also push the supplied YAML as a new config.
Safety
- Always confirm with the operator before deleting. Deletion is immediate and removes the config from HA storage.
- Deletion does not check for sensitive entities — the automation is already gone, there is nothing to gate.
- After deletion, the automation will no longer fire. The entity_id remains in the registry until reload.
Read more
name: ha-delete-config description: Delete an automation or script from Home Assistant via REST API with operator confirmation. Use when the operator asks to remove, delete, or disable a specific automation or script. allowed-tools: - Bash - Read
Delete HA Config
Removes an automation or script from Home Assistant via `DELETE /api/config/{domain}/config/{id}`.
Steps
1. **Identify the target**: Ask the operator which automation or script to delete (name or ID).
- If unknown, list options: `${CLAUDE_PLUGIN_ROOT}/bin/ha-agent-lab ha list-automations` or `ha list-scripts`.
- Each entry under `automations` (or `scripts`) carries `id`, the config ID needed for deletion. `friendly_name` shows the UI display name (this is HA's `friendly_name` attribute, which may differ from the YAML `alias:` field if the operator customized it via the UI).
- `deletable` is `false` for YAML-packaged automations (no numeric `id`): these cannot be removed via REST. Tell the operator to delete the YAML block from their config files and reload manually instead.
2. **Preview**: Show the target details (entity_id, id, friendly_name, state). This action cannot be undone via CLI.
3. **Delete**: Run the appropriate command:
- `${CLAUDE_PLUGIN_ROOT}/bin/ha-agent-lab ha delete-automation <id>` for automations.
- `${CLAUDE_PLUGIN_ROOT}/bin/ha-agent-lab ha delete-script <id>` for scripts.
4. **Check result**:
- `OK`: config deleted. The entity stays in the registry until the next reload.
- `{"status":"not_found","reason":"no_config"}`: the ID doesn't exist in HA.
- `{"error":...}`: surface the error to the operator.
5. **Reload (optional)**: After deletion the entity stays in the registry until the next reload. Offer to trigger one:
- Tell the operator to go to **HA Developer Tools → Services → `automation.reload`** (or `script.reload`).
- Do **not** use `validate-apply` for this — it would also push the supplied YAML as a new config.
Safety
- Always confirm with the operator before deleting. Deletion is immediate and removes the config from HA storage.
- Deletion does not check for sensitive entities — the automation is already gone, there is nothing to gate.
- After deletion, the automation will no longer fire. The entity_id remains in the registry until reload.
Run an always-on Claude Code agent on your own machine, for you or your team. Start and orchestrate sessions from chat in any project it can reach. Take over the same session in the Claude app or the CLI.
Other skills on hermitd.
More skills from other plugins.
browser-use
Direct browser control via CDP for web interaction: automation, scraping, testing, screenshots, and site/app work. Also covers…
agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling…
Questions about ha-delete-config.
- Which coding agents can use ha-delete-config?
- ha-delete-config installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.

