gtapps/hermit-hand-back
plugins/claude-code-hermit/skills/hermit-hand-back/SKILL.md
Summarizes what the operator did during takeover (via git log), optionally queues instructions in NEXT-TASK.md, updates SHELL.md, and restarts the Docker container. Run locally after a /hermit-takeover session.
$ install --global
skillsauthnpx skillsauth add gtapps/claude-code-hermit hermit-hand-backInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 4, 2026, 3:40 AM136.1s1 file scanned
SKILL.md
- name:
- hermit-hand-back
- description:
- Summarizes what the operator did during takeover (via git log), optionally queues instructions in NEXT-TASK.md, updates SHELL.md, and restarts the Docker container. Run locally after a /hermit-takeover session.
Hermit Hand-Back
Hand control back to the autonomous hermit after an operator takeover session. Summarizes what you did, optionally leaves instructions, and restarts the container.
Plan
0. Refuse to run inside the hermit container
This skill is host-only — hand-back restarts the hermit container after a takeover session.
Run: [ -f /.dockerenv ] || [ -f /run/.containerenv ] && echo container || echo host
If the output is container, stop immediately — do not proceed to step 1. Print:
Hand-back restarts the hermit container after a takeover session. You're already inside the hermit — there is nothing to hand back to. Run this from your host shell after a takeover session ends.
1. Verify takeover state
Read .claude-code-hermit/sessions/SHELL.md and check for the **Takeover:** timestamp line.
- If found: extract the takeover timestamp for use in step 2
- If not found: warn "No takeover timestamp found in SHELL.md — proceeding anyway." Use a fallback of 24 hours ago for the git log.
2. Summarize operator activity
Build a summary of what happened during the takeover using git:
- Run
git log --oneline --since="<takeover_timestamp>"to get commits made during takeover - If there are commits: use the oldest commit's parent as the anchor — run
git log --oneline --since="<takeover_timestamp>" --format="%H" | tail -1to get the first takeover commit, thengit diff --stat <first_commit>^..HEADfor a file change summary - Format as a concise summary:
- "3 commits during takeover: fixed auth bug, updated README, bumped version. 5 files changed."
- Or: "No commits during takeover." (operator may have just explored, tested, or reviewed)
3. Ask for instructions
Ask the operator: "Any instructions for the hermit to work on next?"
- If yes: write the instructions to
.claude-code-hermit/sessions/NEXT-TASK.md. This file is automatically picked up at the next session-start. - If no / skip: don't create or modify NEXT-TASK.md
4. Update SHELL.md
- Add a progress log entry summarizing the takeover:
[HH:MM] Operator takeover — <git summary from step 2>. <Instructions queued / No specific instructions.> - Change
**Status:**fromoperator_takeovertoidle - Remove the
**Takeover:**timestamp line
5. Restart the container
Run .claude-code-hermit/bin/hermit-docker up in the project root.
Check that the container started: run docker compose -f docker-compose.hermit.yml ps --status running after a few seconds.
- If running: confirm success
- If not running: warn "Container didn't start — check
.claude-code-hermit/bin/hermit-docker logsfor errors."
6. Confirm hand-back
Print confirmation:
Hermit is back online.
Takeover summary: <git summary>
Instructions: <queued / none>
Check status anytime: .claude-code-hermit/bin/hermit-status
Related Skills
gtapps/ha-presence-report
tools
VerifiedTrustedCommunity
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.
59SKILL.mdUpdated Jun 4, 2026
gtapps/ha-evening-brief
development
VerifiedTrustedCommunity
Evening house brief — end-of-day security check, device status, and energy snapshot. Runs as a daily routine at 22:30 or on demand.
59SKILL.mdUpdated Jun 4, 2026
gtapps/ha-automation-explorer
tools
VerifiedTrustedCommunity
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."
59SKILL.mdUpdated Jun 4, 2026
gtapps/domain-brainstorm
tools
VerifiedTrustedCommunity
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.
59SKILL.mdUpdated Jun 4, 2026