What problem does it solve? Operators running the per-machine redskilled execution daemon need a single guided workflow to inspect status, provision the host, configure machine policy, restart safely, and diagnose why a Worker on a given issue stalled or never started. ## Core Features & Use Cases - Daemon lifecycle operation: Read provisioning audits and host state, provision the daemon home and OS service, configure worker/memory/validation ceilings and GitHub credential profiles in ~/.red/config.yaml, and restart through the idempotent provisioning command. - Self-upgrading daemon guidance: Distinguishes a daemon that is merely behind the registry (wait one replace interval) from a wedged daemon (stop and re-provision), preventing harmful manual restarts. - Issue-keyed Worker debugging: Resolves an issue number to every Worker that touched it via MCP tools and log lanes, then writes a self-serve debug dossier to .red/tmp/diagnostics/ with fiche, event sequence, log excerpts, diagnosis, and next moves. - Use Case: An operator runs /redskilled 3351 to learn why the Worker on issue 3351 never started, and receives a dossier showing the daemon's refused-over-worker-ceiling admission verdict plus the exact recovery commands to run. ## Quick Start Ask the assistant to operate the redskilled daemon with no argument, or pass an issue number like 3351 to debug that issue's Worker and produce a diagnostic dossier.