From 54b4435aaa3e9483fe0ff78f6f655d9b8d82acac Mon Sep 17 00:00:00 2001 From: zap Date: Mon, 9 Mar 2026 19:00:40 +0000 Subject: [PATCH] feat(skills): add inbox-priority-agent triage skill --- skills/inbox-priority-agent/SKILL.md | 62 +++++++++++++++++++ .../references/priority-rubric.md | 56 +++++++++++++++++ 2 files changed, 118 insertions(+) create mode 100644 skills/inbox-priority-agent/SKILL.md create mode 100644 skills/inbox-priority-agent/references/priority-rubric.md diff --git a/skills/inbox-priority-agent/SKILL.md b/skills/inbox-priority-agent/SKILL.md new file mode 100644 index 0000000..e352ce2 --- /dev/null +++ b/skills/inbox-priority-agent/SKILL.md @@ -0,0 +1,62 @@ +--- +name: inbox-priority-agent +description: Triage inbound messages and produce a priority-ordered action list with concise draft replies. Use when the user asks to review inboxes, mentions, DMs, email summaries, or mixed inbound queues; when they want urgency/importance sorting; or when they want low-noise recommendations in a Now/Soon/Watch format without sending anything automatically. +--- + +# Inbox Priority Agent + +## Overview +Prioritize inbound communication into a short action queue, then suggest clear next moves and optional draft responses. Optimize for signal over noise and avoid unnecessary pings. + +## Workflow + +1. Collect context + - Identify source(s): chat, email, mentions, notifications, or mixed inbox. + - Capture sender, timestamp, thread context, and explicit deadlines. + +2. Classify each item + - Score urgency and importance using `references/priority-rubric.md`. + - Assign one level: `P1` (critical), `P2` (important), `P3` (normal), `P4` (low/no action). + - Mark confidence as `high`, `medium`, or `low` when context is incomplete. + +3. Deduplicate and compress + - Merge duplicate notifications and same-topic follow-ups. + - Suppress low-value repeats unless status changed. + +4. Build briefing output + - Present sections in this order: + - `Now` (P1) + - `Soon` (P2) + - `Watch` (P3/P4 changes worth awareness) + - `Next actions` (numbered, minimal, concrete) + - Keep each bullet to one short line. + +5. Draft replies only when useful + - Include drafts for P1/P2 items or when explicitly requested. + - Keep drafts short, polite, and directly actionable. + - Never send external messages automatically unless explicitly instructed. + +## Output Template +Use this exact structure unless the user requests another format. + +- **Now** + - [item] — why it matters + deadline/risk +- **Soon** + - [item] — why it matters + recommended window +- **Watch** + - [item] — context only / no immediate action +- **Next actions** + 1. [concrete action] + 2. [concrete action] + +If drafts are included, append: + +- **Draft replies** + - To [name/channel]: "[draft]" + +## Guardrails +- Do not fabricate missing context; label assumptions clearly. +- Prefer fewer, higher-signal recommendations over exhaustive dumps. +- If uncertain between two priorities, choose the higher one and note uncertainty. +- Treat private/sensitive data minimally and avoid unnecessary quoting. +- Ask before any state-changing external action (send/reply/post). diff --git a/skills/inbox-priority-agent/references/priority-rubric.md b/skills/inbox-priority-agent/references/priority-rubric.md new file mode 100644 index 0000000..de4b987 --- /dev/null +++ b/skills/inbox-priority-agent/references/priority-rubric.md @@ -0,0 +1,56 @@ +# Priority Rubric + +Use this rubric to map inbound items to a single priority level. + +## Scoring Dimensions + +Score each dimension 0-3, then sum. + +- **Urgency (0-3)** + - 3: Needs action now or within 2 hours + - 2: Needs action today + - 1: Needs action this week + - 0: No clear time pressure + +- **Importance (0-3)** + - 3: High impact on commitments, money, safety, or key relationships + - 2: Meaningful impact on active goals/projects + - 1: Useful but non-critical + - 0: Minimal impact + +- **Consequence of delay (0-3)** + - 3: Major downside if delayed (missed deadline, escalation) + - 2: Moderate downside + - 1: Minor downside + - 0: No meaningful downside + +## Priority Mapping + +- **P1 (Now):** total 7-9, or explicit hard deadline <= 2h +- **P2 (Soon):** total 5-6, or hard deadline today +- **P3 (Watch):** total 3-4 +- **P4 (Low):** total 0-2 + +## Tie-Breakers + +If two items tie, rank higher when one has: +1. Explicit deadline +2. Direct ask from a high-priority stakeholder +3. Thread with unresolved blocker +4. Higher recency (newer unresolved item) + +## Draft Reply Patterns + +Use concise variants: + +- **Acknowledge + ETA** + - "Got this — I’ll send you an update by [time]." + +- **Clarify blocker** + - "I can do this next, but I need [missing info] first." + +- **Defer politely** + - "Noted. I can take this on [day/time] unless priorities change." + +- **Escalate responsibly** + - "This looks time-sensitive. Recommending we handle it first because [reason]."