What problem does it solve? Setting up ongoing monitoring of Slack threads, DMs, schedules, email, Jira, GitHub, Telegram, or X activity requires creating a correctly structured quest folder with four files (meta.json, watch.json, timeline.ndjson, context.md). Hand-writing these files causes schema errors like wrong IDs or missing fields; this Skill scaffolds them correctly through a validated script. ## Core Features & Use Cases - Interactive quest scaffolding: Gathers title, watch targets, priority, and context from the user, then creates the quest via the sq new-quest script with full validation. - Multi-source watch types: Supports slack_thread, slack_channel, slack_dm, slack_mention, schedule (cron or one-shot), email, jira, github_pr, github_issue, telegram, and x watches with per-type required fields. - Pre-dispatch filters: Configures filter_user_ids and filter_keywords on Slack watches so irrelevant messages never wake the worker. - Use Case: A user pastes a Slack permalink and says "track this thread for the partner's reply." The Skill extracts channel_id and thread_ts, confirms details, and creates a quest that the triage loop picks up on its next tick. ## Quick Start Ask the assistant to create a quest that watches a specific Slack thread or channel, providing the permalink and a short description of what to track.
