What problem does it solve? When the worker — the component that actually executes jobs for the MyCity marketplace — stops, crashes, silently drops jobs, or fails to publish memory, this Skill provides a structured deep-diagnosis procedure to find the true root cause instead of guessing from surface symptoms. ## Core Features & Use Cases - Eleven-dimension inspection: Covers systemd services and timers, job queue age analysis, atomic job claiming, orphaned job recovery, file locks, git alignment, pause kill-switch behavior, AI engine quota/credentials, disk and memory health, and the VPS self-report bridge. - Evidence-based diagnosis: Distinguishes what can be proven from the VPS versus what can only be inferred remotely from Supabase queue traces and git commit cadence, marking every finding as proven, broken, or not observable. - Structured outputs: Writes defects with root cause and behavioral verification tests into the repair backlog, produces an impact-ordered audit report, and prepares exact paste-ready commands for actions only the human owner can perform. - Use Case: The chat stops responding and the dashboard shows stale data. Use this Skill to trace whether the cause is a crashed service, a stuck in-progress job, an expired AI session, or unpublished VPS commits. ## Quick Start Use the worker skill to diagnose why the worker has stopped picking up jobs from the queue and produce a root-cause report.