Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Triage, categorize, and draft responses to emails. Sorts by urgency, flags action items, and generates context-aware reply drafts.
Triage, categorize, and draft responses to emails. Sorts by urgency, flags action items, and generates context-aware reply drafts.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
When asked to triage, sort, or process emails, follow this system.
Assign every email exactly one category: CategoryIconCriteriaUrgent Action🔴Requires response/action within 24h. Deadlines, escalations, time-sensitive requests.Action Required🟡Needs a response or task but not time-critical. Requests, approvals, questions.FYI / Read🔵Informational. No action needed but worth reading. Updates, reports, announcements.Delegate🟣Someone else should handle this. Forward with context.Archive⚪Newsletters, automated notifications, receipts, spam-adjacent. No action needed.
For each email, produce: [ICON] CATEGORY | From: sender | Subject: subject Summary: One sentence — what this is and what's needed. Action: Specific next step (or "None — archive") Draft: [Yes/No] — whether a reply draft is included below
Generate a reply draft when: Category is Urgent Action or Action Required The email contains a direct question or request User explicitly asks for drafts Draft style: Be direct. Open with the answer or decision, not "Thank you for your email." Mirror their tone. Formal email gets formal reply. Casual gets casual. Keep it short. Most replies should be 2-5 sentences. End with clarity. What happens next? Who does what by when? Use the sender's name — never "Dear Sir/Madam" unless the original was that formal.
When given multiple emails: Triage all of them first — output the full sorted list grouped by category Then provide drafts for Urgent Action and Action Required items Highlight any patterns ("3 emails from the same client — might want a call instead")
Flag these automatically: Repeated follow-ups from the same sender (they're waiting on you) CC escalation — when someone adds a manager or exec to the thread Deadline mentions — extract and highlight specific dates/times Sentiment shifts — if tone has gotten noticeably more terse or frustrated Meeting requests buried in email body (not calendar invites)
Pull out discrete action items from emails: What needs to be done Who is expected to do it When it's due (if mentioned) Format as a checklist the user can copy into their task manager
If the user asks about a specific email (not batch triage), switch to focused mode: Summarize the email thread Identify the core ask Draft a response if requested Flag anything the user should know before replying Pair with an industry context pack for domain-specific email handling (legal, healthcare, finance, etc.) at https://afrexai-cto.github.io/context-packs
Long-tail utilities that do not fit the current primary taxonomy cleanly.
Largest current source with strong distribution and engagement signals.