What problem does it solve? When the Sonder Runtime breaks — tests fail with connection refused, the server won't start, Ollama is unreachable, or a database locks — engineers waste time guessing causes. This Skill maps each known failure symptom to ranked likely causes plus the cheapest discriminating experiment that splits hypothesis A from B. ## Core Features & Use Cases - Symptom-to-fix triage index: Thirteen sections covering test failures, import errors, server startup, doctor/preflight checks, Ollama connectivity, database locks, disk exhaustion, selfmod breakage, and Windows encoding issues. - Discriminating experiments: Each section gives the cheapest command that distinguishes competing hypotheses, with what each outcome means. - Runbook pointers and provenance: Links to docs/runbooks/ procedures and grep commands to re-verify volatile claims against the codebase. - Use Case: A developer sees "database is locked" during a test run. The Skill directs them to identify the store, run PRAGMA integrity_check on a stopped service to distinguish lock contention from corruption, then follow the appropriate runbook. ## Quick Start Ask the assistant to triage why the Sonder server won't start or why tests fail with connection refused, and it will walk through the ranked causes and discriminating commands.
