skills/hermit-takeover/SKILL.md
Stops the Docker container running the autonomous hermit, marks the session as operator takeover, loads full hermit context, and presents a summary. Run locally (outside Docker) when you want to drive interactively.
npx skillsauth add gtapps/claude-code-hermit hermit-takeoverInstall 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.
Stop the autonomous hermit and take the wheel. This skill is for Docker-based always-on setups — it stops the container, preserves all session state, and loads the hermit's context so you can work interactively with full continuity.
Read .claude-code-hermit/config.json to get:
tmux_session_name — resolve {project_name} with the actual project directory nameagent_name — for displayRun docker compose -f docker-compose.hermit.yml ps --status running --format '{{.Name}}' in the project root.
docker compose fails (Docker not installed or no compose file): inform the operator: "No docker-compose.hermit.yml found. This skill is for Docker-based setups." and stop.Run docker compose -f docker-compose.hermit.yml stop (not down — we want to preserve the container for restart).
This sends SIGTERM, which triggers the entrypoint to exit cleanly. If hermit-stop runs inside the container, it archives the current report before exiting.
Wait briefly for the container to stop: check docker compose -f docker-compose.hermit.yml ps --status running up to 3 times with 5-second intervals. If it's still running after 15 seconds, warn: "Container is still stopping — it may take a moment for the session to archive."
Read .claude-code-hermit/sessions/SHELL.md.
If the file exists and has content:
**Status:** line and change the value to operator_takeover- **Takeover:** YYYY-MM-DD HH:MM with the current timestampIf SHELL.md doesn't exist or is empty: note this for the summary — the hermit may have been idle with no active session.
Read these files (all in parallel):
.claude-code-hermit/OPERATOR.md — the project rulebook.claude-code-hermit/sessions/SHELL.md — current/last session stateS-*-REPORT.md in .claude-code-hermit/sessions/ (by filename sort, descending)Print a structured summary for the operator:
Takeover complete.
Session: S-NNN | was: in_progress
Task: "Add input validation to API endpoints"
Progress: 2/4 tasks completed (via TaskList)
Blockers: none
Cost so far: $1.80
You're now driving. The hermit's full context is loaded.
When you're done, run /claude-code-hermit:hermit-hand-back to restart the hermit.
Adapt based on what's actually in SHELL.md:
The session continues normally from here. The operator works interactively with the full hermit context loaded.
tools
Presence history & tracker-health report — current home/away state, reliability, recent arrival/departure transitions, and activity patterns for person/device_tracker entities. Use when the operator asks about presence history or when a presence-dependent automation (locks, alarm, vacuum, climate) misbehaves.
development
Evening house brief — end-of-day security check, device status, and energy snapshot. Runs as a daily routine at 22:30 or on demand.
tools
Browse and explain the hermit's Home Assistant automations — list by topic, filter by keyword with plain-language YAML explanations, or sort by last-fired. Read-only. Use when the operator asks "what automations do I have / what does this one do / which haven't fired."
tools
On-demand HA-voice brainstorm — reads entity inventory, automation/script listings, and operator intent to surface at most 2 capability-gap ideas, each gated by proposal-triage before becoming a PROP. Invoke when the operator asks "what automations am I missing?", "any coverage gaps?", or "brainstorm improvements". Never runs autonomously.