email-triage
The email-triage skill categorizes inbox messages into urgent, needs-reply, receipts, and archive-safe groups, providing brief action plans for each category. Use this skill when you need to process and organize incoming emails efficiently, with optional dry-run capabilities before making any mailbox changes.
git clone --depth 1 https://github.com/clawdotnet/openclaw.net /tmp/email-triage && cp -r /tmp/email-triage/src/OpenClaw.Gateway/skills/email-triage ~/.claude/skills/email-triageSKILL.md
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.
Organizes repository documentation and keeps new docs in the correct location.
Produce a daily news brief (AI/security/dev) with links, key takeaways, and action items.
Connects to databases, runs SQL queries, and analyzes datasets using code to provide actionable business insights.
Conducts comprehensive web research, synthesizes data from multiple sources, and produces detailed reports.
Safely operate Home Assistant by resolving targets first and validating state before writes.
Safely interact with MQTT topics with allow/deny policies and minimal payload risk.
Operates as an autonomous software engineer, capable of writing code, running tests, and managing git repositories.