mail-triagelisted

# Mail Triage — Skill Instructions ## What this skill does Exhaustive triage of both mail inboxes over a configurable window (default **7 days**). For each thread: resolve the sender/subject against HAL CRM context and the Obsidian jobsearch vault, classify into a domain-specific category, and recommend a concrete action. **Parameter**: `N=<days>` in the prompt overrides the default window (e.g. "trie mes mails des 3 derniers jours"). **Relationship with `morning-briefing`**: that skill does a lightweight, daily-integrated mail pass (Steps 1e/1f) — sufficient for a briefing, not for dedicated triage. This skill is intentionally deeper: exhaustive scan, explicit per-thread classification, action recommendations. The two skills are independent by design — running both in the same session is valid (different depth and goal). Do NOT attempt to call this skill from inside `morning-briefing` to consolidate logic — the shallow pass in the briefing is intentionally faster and context-lighter. Any backend that is unreachable renders a loud `⚠️ <source> DOWN — <reason>` line. Silent omission is a critical failure. --- ## Step 0 — Pre-flight Probe each backend independently. Do NOT bail on the first failure — all probes run regardless. - **hal-mcp probe**: call `mcp__plugin_hal_hal-mcp__whoami`. Assert **resolvability, not identity**: it must answer and return at least one workspace in `workspaces[]`. On call failure → mark `hal:DOWN <reason>`, skip Steps 1a-1c. If it answers b