inbox-triage

Topics in the source

• Inbox-Triage — Recurring Email Triage
• Invocation Triggers
• Prerequisites
• DRAFTS ONLY — Never Send
• Step 0: Grill-Me Intake (Light — 0–2 Optional Override Questions)
• Q1 (optional, asked only when on-demand run is outside normal cadence)
• Q2 (optional, asked only when user invokes with category-skip intent)
• Step 1: Determine Search Window

Paired with inbox-setup. This skill consumes the 7-file knowledge base that inbox-setup writes at ${WORKSPACE}/Email/. The file contracts MUST match exactly. See references/kbfilecontract.md — this is the mirror of the setup-side contract, viewed from the read side. Run on a recurring schedule (1–3x daily) or on demand. Classify recent emails, research new senders, generate decision recommendations, draft replies (NEVER SEND), deliver a clean report, and update the knowledge base with what was learned this run. "triage my inbox" "inbox triage" "check my email" "run email triage" "process my inbox" "what's new in my email" "handle my email" "email triage" Required reads at start (fail-fast if missing): Core (required): ${WORKSPACE}/Email/email-taxonomy.md — classification + report preferences ${WORKSPACE}/Email/email-patterns.md — voice, persona, templates, hard rules Optional core (read if exists): ${WORKSPACE}/Email/evaluation-framework.md ${WORKSPACE}/Email/rate-card.md Evolving (read AND update every run): ${WORKSPACE}/Email/blocklist.md ${WORKSPACE}/Email/tracker.md Output: ${WORKSPACE}/Email/triage-log/ - .md — per-run log If any core required file is missing → halt, direct us

This is an excerpt. Refer to the complete source and its current requirements.