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.tools
Composes and delivers the daily fitness brief — a forward-looking morning read (readiness + today's plan) or a backward-looking evening read (today's training, or an earned-rest note, + tomorrow's setup) — in the operator's configured voice. Invoke with /claude-code-fitness-hermit:fitness-brief --morning|--evening|--slot <name>. Becomes the plugin's two daily beats — the morning Strava connectivity check and the evening activity sync, RPE binding, and Run deep-dive.
development
Renew the hermit's long-lived Claude login token over the channel, before it expires. Relays a one-time sign-in link to the operator, takes the code back, installs the new token, and restarts. Activates on messages like 'relogin', 'renew my login', 'reauth', 'the login is expiring', or when doctor's credential-expiry check flags setup-token.
development
Synthesizes the past 7 days of archived briefs into a weekly digest — top stories, emerging vs faded themes, category activity, and per-source performance built from archive frontmatter. Delivers to the operator's configured channel and archives a weekly note. Designed as a weekly routine. Invoke with /feed-hermit:weekly-digest.
development
Manage developing story arcs tracked across briefs — add, resolve, and list active arcs in compiled/story-arcs-*.md. Arc Watch keywords drive the feed-brief arc-tagging enrichment. Invoke with /feed-hermit:story-arcs add|resolve|list.