email-triage

star 369

Triage inbox into “needs reply”, “FYI”, “urgent”, and “safe to archive”, with a short plan for each.

clawdotnet By clawdotnet schedule Updated 2/27/2026

name: email-triage description: Triage inbox into “needs reply”, “FYI”, “urgent”, and “safe to archive”, with a short plan for each. metadata: {"openclaw":{"emoji":"📧"}}

When asked to triage email:

  1. Default to read-only / dry-run behavior unless explicitly asked to modify mailboxes.
  2. If available, use inbox_zero:
    • Start with analyze (or categorize) to summarize categories and urgency.
    • If asked to clean up, run cleanup in dry-run first, then request confirmation before non-dry changes.
  3. Produce a concise report:
    • Urgent (why + suggested reply)
    • Needs reply (draft 1–3 sentence reply)
    • Receipts/confirmations (extract key numbers/dates)
    • Newsletters/promotions (safe to archive)
  4. If asked to email the report, send it via the email tool with a clear subject line.
Install via CLI
npx skills add https://github.com/clawdotnet/openclaw.net --skill email-triage
Repository Details
star Stars 369
call_split Forks 70
navigation Branch main
article Path SKILL.md
More from Creator