plugins/claude-code-homeassistant-hermit/skills/ha-delete-config/SKILL.md
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.
npx skillsauth add gtapps/claude-code-hermit ha-delete-configInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Removes an automation or script from Home Assistant via DELETE /api/config/{domain}/config/{id}.
Identify the target: Ask the operator which automation or script to delete (name or ID).
${CLAUDE_PLUGIN_ROOT}/bin/ha-agent-lab ha list-automations or ha list-scripts.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).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.Confirm with operator: Show the target details (entity_id, id, friendly_name, state) and ask for explicit confirmation before proceeding. This action cannot be undone via CLI.
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.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.Reload (optional): After deletion the entity stays in the registry until the next reload. Offer to trigger one:
automation.reload (or script.reload).validate-apply for this — it would also push the supplied YAML as a new config.data-ai
Initializes or resumes a work session. Loads context from OPERATOR.md and SHELL.md, orients the agent, and establishes what to work on. Use at the beginning of every work session.
tools
Evolves hermit configuration and templates after a plugin update. Detects version gaps, presents new features, walks through new settings. Run after updating the plugin.
testing
Initializes the autonomous agent in the current project. Creates the state directory, templates, OPERATOR.md, and config.json. Appends session discipline to CLAUDE.md. Detects installed hermits. Run once per project, like git init.
tools
Generates Docker scaffolding and walks the operator through the full deployment — token setup, build, start, MCP plugin configuration, workspace trust, and verification. Offers to back up and overwrite existing Docker files. Run after /hatch.