← ClaudeAtlas

keep-awake-inspectlisted

Inspect and diagnose the keep-awake-linux plugin — state, log, inhibitors, recent activity.
hk9890/claude-dev-tools · ★ 0 · AI & Automation · score 73
Install: claude install-skill hk9890/claude-dev-tools
## What this skill does Produce a structured report of the keep-awake-linux plugin's **current state** and **recent activity**, by reading raw state files and the log directly. Does NOT depend on the `keep-awake` binary being on `$PATH`. This inspection is a read-only post-mortem: observe state, never actuate it — no new inhibitors, no kills, no state-file edits, no `keep-awake start|stop|hook` calls — unless the user explicitly asks for cleanup, and confirm first when they do. ## Hard rule NEVER run any of these during inspection: ``` systemctl suspend systemctl hibernate systemctl poweroff systemctl reboot loginctl suspend loginctl hibernate ``` The plugin's contract is "register an inhibitor with logind". Triggering an actual suspend is out of scope for inspection. ## Workflow Run Steps 1–3 in a single shell invocation — `$STATE_DIR` and `$LOG` do not persist across separate tool calls. ### Step 0 — Check tool availability ```bash command -v systemd-inhibit >/dev/null 2>&1 || echo "systemd-inhibit MISSING" ``` If `systemd-inhibit` is missing, note it as an environmental issue (the helper itself no-ops in this case) and skip the logind cross-check and the orphan check below — rely on PID markers and the log alone. Do not stop; the rest of the inspection still works. ### Step 1 — Resolve the state directory Mirror the helper's resolution exactly (`bin/keep-awake` uses the XDG dir unconditionally whenever `XDG_RUNTIME_DIR` is set — it does not fall back to `/tmp`