Skip to content
Back to skills

Ha Delete Config

ASecurity

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.

  • 74 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added May 27, 2026
data-aigobashapi

Works with

  • cli
  • api

Security analysis

A100/100

Scanned September 20, 2026

npx -y skills add gtapps/claude-code-hermit --skill ha-delete-config --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Ha Delete Config?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Ha Delete Config
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/gtapps-ha-delete-config/badge)](https://www.skillsdirectory.com/skills/gtapps-ha-delete-config)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
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`.
   - The `id` column is the config ID needed for deletion. The `friendly_name` column 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).
   - The `deletable` column 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**: Read the JSON output.
   - `ok: true` — config deleted. The entity stays in the registry until the next reload.
   - `ok: false, message: "Resource not found"` — the ID doesn't exist in HA (note: HA returns 400, not 404).
   - `ok: false` + other message — 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.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.