What problem does it solve? Operating and extending the Sidequestor yaas triage system requires understanding its checker plugin architecture, watch schemas, watermark lag handling, and state file layout, which are otherwise scattered across many scripts and directories. ## Core Features & Use Cases - Checker Plugin Reference: Explains how per-watch-type checker scripts in checkers/ are invoked by the orchestrator, their output contract (0|, N|<preview>, error|<reason>), and how to add new channel types like Slack, email, Jira, GitHub, Telegram, and X. - State and Schema Documentation: Details the watch.json and meta.json schemas, watermark lag files, quest folder lifecycle, and the approval ledger workflow. - Operations Runbook: Covers setup, launchd control, configurable .env knobs (spend ceilings, dispatch fanout, backoff), and a symptom-to-fix debugging table. - Use Case: When asked to add a new watcher type or debug why a quest never fires, load this Skill to get the exact checker contract, environment variables, and diagnostic commands. ## Quick Start Ask the agent to explain how to add a new checker type to the yaas triage system and what output contract it must follow.
