The watchdog-watchdog — one read-only pass that proves the resume watchdog (the n1 layer that revives dead autonomous Claude sessions) is itself ALIVE, TICKING, and reviving PRODUCTIVE instances, versus silently STALLED. Distrusts self-report: reads the live Fleet registry ledgers (%LOCALAPPDATA%\Fleet\registry), the scheduled-task exit codes AND each task's Principal.LogonType, never the watchdog's own "I'm fine". Verifies the n2 layer (is the watchdog ticking, is its backlog draining, are resumes witnessed as real transcript turns, or merely launchedunproven) and the n3 layer (is THIS audit itself scheduled/looped and orthogonal to the failure it detects — who watches the watchman's watchman). Turnkey entry point: tools\watchdogwatchdogaudit.ps1 (read-only, emits GREEN/AMBER/RED + exit 0/2/3). Catches the exact failure this repo hit on 2026-07-09: after a boot the watchdog drained the backlog, then every scheduled task with Principal.LogonType=Interactive began returning 0x800710E0 ("operator or administrator refused the request") on this RDP/headless box while S4U siblings stayed 0x0 — an 11-task outage of the whole safety net, leaving resumes launched-but-unproven. CORRECTED ROOT CAUSE: the discriminator is LogonType (Interactive dies, S4U survives), NOT the conhost launch shim (that theory was empirically disproved — the watchdog kept failing after conhost was removed). Read-only by default; the S4U migration + live drain are operator/elevation-gated. Use after a crash/reboot, when sessions look stuck, or on a /loop cadence as the standing meta-watchdog.
Install with
Claude CodeCodexCursorGitHub CopilotGemini CLI
Supported by the Atlas install prompt. Skill-specific requirements vary.
Skill stats
Skills1CategoryContent & writingStars0
About this skill
The watchdog-watchdog — one read-only pass that proves the resume watchdog (the n1 layer that revives dead autonomous Claude sessions) is itself ALIVE, TICKING, and reviving PRODUCTIVE instances, versus silently STALLED. Distrusts self-report: reads the live Fleet registry ledgers (%LOCALAPPDATA%\Fleet\registry), the scheduled-task exit codes AND each task's Principal.LogonType, never the watchdog's own "I'm fine". Verifies the n2 layer (is the watchdog ticking, is its backlog draining, are resumes witnessed as real transcript turns, or merely launchedunproven) and the n3 layer (is THIS audit itself scheduled/looped and orthogonal to the failure it detects — who watches the watchman's watchman). Turnkey entry point: tools\watchdogwatchdogaudit.ps1 (read-only, emits GREEN/AMBER/RED + exit 0/2/3). Catches the exact failure this repo hit on 2026-07-09: after a boot the watchdog drained the backlog, then every scheduled task with Principal.LogonType=Interactive began returning 0x800710E0 ("operator or administrator refused the request") on this RDP/headless box while S4U siblings stayed 0x0 — an 11-task outage of the whole safety net, leaving resumes launched-but-unproven. CORRECTED ROOT CAUSE: the discriminator is LogonType (Interactive dies, S4U survives), NOT the conhost launch shim (that theory was empirically disproved — the watchdog kept failing after conhost was removed). Read-only by default; the S4U migration + live drain are operator/elevation-gated. Use after a crash/reboot, when sessions look stuck, or on a /loop cadence as the standing meta-watchdog.
Quick start
Copy the install prompt. Use the green button above this README.
Send it to your agent. Paste it into your coding agent’s chat and send.
Review the setup. Your agent checks the skill’s instructions, requirements, and installation scope.
The watchdog-watchdog — one read-only pass that proves the resume watchdog (the n¹ layer that revives dead autonomous Claude sessions) is itself ALIVE, TICKING, and reviving PRODUCTIVE instances, versus silently STALLED. Distrusts self-report: reads the live Fleet registry ledgers (%LOCALAPPDATA%\Fleet\registry), the scheduled-task exit codes AND each task's Principal.LogonType, never the watchdog's own "I'm fine". Verifies the n² layer (is the watchdog ticking, is its backlog draining, are resumes witnessed as real transcript turns, or merely launched_unproven) and the n³ layer (is THIS audit itself scheduled/looped and orthogonal to the failure it detects — who watches the watchman's watchman). Turnkey entry point: tools\watchdog_watchdog_audit.ps1 (read-only, emits GREEN/AMBER/RED + exit 0/2/3). Catches the exact failure this repo hit on 2026-07-09: after a boot the watchdog drained the backlog, then every scheduled task with Principal.LogonType=Interactive began returning 0x800710E0 ("operator or administrator refused the request") on this RDP/headless box while S4U siblings stayed 0x0 — an 11-task outage of the whole safety net, leaving resumes launched-but-unproven. CORRECTED ROOT CAUSE: the discriminator is LogonType (Interactive dies, S4U survives), NOT the conhost launch shim (that theory was empirically disproved — the watchdog kept failing after conhost was removed). Read-only by default; the S4U migration + live drain are operator/elevation-gated. Use after a crash/reboot, when sessions look stuck, or on a /loop cadence as the standing meta-watchdog.
About this listing
Category
Content & writing
Reported license
Apache-2.0
Listing language (estimated)
English
Review status
Not individually reviewed
Agent compatibility
Atlas installation supports Claude Code, Codex, and Cursor. Skill-specific dependencies and features are checked during setup.