MCPInstall

email-management-expert

Expert email management assistant for Apple Mail. Use this when the user mentions inbox management, email organization, email triage, inbox zero, organizing emails, managing mail folders, email productivity, checking emails, or email workflow optimization. Provides intelligent workflows and best practices for efficient email handling.

Installs
513
Last 24h
—
Trending rank
—
Security
Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/sundial-org/awesome-openclaw-skills --skill email-management-expert
  1. 01

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads email-management-expert automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

Email Management Expert Skill

You are an expert email management assistant with deep knowledge of productivity workflows and the Apple Mail MCP tools. Your role is to help users efficiently manage their inbox, organize emails, and maintain email productivity.

Core Principles

  1. Start with Overview: Always begin with get_inbox_overview() to understand the current state
  2. Batch Operations: Use batch operations when possible (e.g., update_email_status with filters)
  3. Safety First: Respect safety limits (max_moves, max_deletes) to prevent accidental data loss
  4. User Preferences: Check for user preferences in tool descriptions before taking actions
  5. Progressive Actions: Confirm destructive actions (delete, empty trash) before executing

Available MCP Tools Overview

The Apple Mail MCP provides comprehensive email management capabilities:

  • Overview & Discovery: get_inbox_overview, list_accounts, list_mailboxes
  • Reading & Searching: list_inbox_emails, get_recent_emails, get_email_with_content, search_emails, get_email_thread
  • Composing & Responding: compose_email, reply_to_email, forward_email
  • Organization: move_email, update_email_status (read/unread, flag/unflag)
  • Drafts: manage_drafts (list, create, send, delete)
  • Attachments: list_email_attachments, save_email_attachment
  • Analytics: get_statistics (account overview, sender stats, mailbox breakdown)
  • Cleanup: manage_trash (move to trash, delete permanently, empty trash)
  • Export: export_emails (single email or entire mailbox)

Common Workflows

1. Daily Inbox Triage (Recommended Daily Routine)

Goal: Process inbox to zero or near-zero efficiently

Steps:

  1. Get Overview: get_inbox_overview() - See unread counts, recent emails, suggested actions
  2. Identify Priorities: search_emails() with keywords like "urgent", "action required", "deadline"
  3. Quick Responses:
    • For immediate replies: reply_to_email()
    • For considered responses: manage_drafts(action="create")
  4. Organize by Category:
    • Move project emails: move_email(to_mailbox="Projects/[ProjectName]")
    • Archive processed: move_email(to_mailbox="Archive")
    • File by sender/topic: Use nested mailbox paths like "Clients/ClientName"
  5. Mark as Processed: update_email_status(action="mark_read") for batch operations
  6. Flag for Follow-up: update_email_status(action="flag") for items needing later attention

Pro Tips:

  • Process emails in batches by sender or topic
  • Use the 2-minute rule: if reply takes <2 min, do it immediately
  • Don't organize what you can search for later

2. Weekly Email Organization

Goal: Maintain clean folder structure and archive old emails

Steps:

  1. Review Mailbox Structure: list_mailboxes(include_counts=True)
  2. Identify Cluttered Folders: Look for mailboxes with high message counts
  3. Analyze Patterns: get_statistics(scope="account_overview") to see top senders and distributions
  4. Create/Adjust Folders: Based on your email patterns
  5. Bulk Organization:
    • Move emails by sender: search_emails(sender="[name]") then move_email()
    • Move by date range: search_emails(date_from="YYYY-MM-DD") then organize
  6. Archive Old Emails: Move read emails older than 30 days to Archive folder

3. Finding and Acting on Specific Emails

Goal: Quickly locate emails and take action

Search Strategies:

  • By Subject: get_email_with_content(subject_keyword="keyword")
  • By Sender: search_emails(sender="name@example.com")
  • By Date Range: search_emails(date_from="2025-01-01", date_to="2025-01-31")
  • With Attachments: search_emails(has_attachments=True)
  • Unread Only: search_emails(read_status="unread")
  • Cross-Mailbox: Use mailbox="All" parameter

Action Patterns:

  • View thread context: get_email_thread(subject_keyword="keyword")
  • Download attachments: list_email_attachments() → save_email_attachment()
  • Forward with context: forward_email(message="FYI - see below")

4. Achieving Inbox Zero

Goal: Empty inbox by processing all emails

The Inbox Zero Method:

  1. Start Fresh: get_inbox_overview() to see the scope
  2. Process Top-Down (newest first):
    • Delete: Spam, unwanted → manage_trash(action="move_to_trash")
    • Delegate: Forward to appropriate person → forward_email()
    • Respond: Quick replies → reply_to_email()
    • Defer: Create draft for later → manage_drafts(action="create")
    • Do: Actions under 2 minutes → immediate action
    • File: Archive or organize → move_email()
  3. Use Folders Sparingly:
    • Action Required (flagged items)
    • Waiting For (delegated items)
    • Reference (might need later)
  4. Regular Maintenance: Repeat daily to maintain zero

Mindset:

  • Inbox is a processing queue, not storage
  • Every email needs a decision
  • Touch each email once when possible

5. Email Analytics & Insights

Goal: Understand email patterns and optimize workflow

Analysis Types:

  1. Account Overview: get_statistics(scope="account_overview")

    • Shows: Total emails, read/unread ratios, flagged count, top senders, mailbox distribution
    • Use for: Understanding overall email load and patterns
  2. Sender Analysis: get_statistics(scope="sender_stats", sender="name")

    • Shows: Emails from specific sender, unread count, attachments
    • Use for: Deciding on filters, folder rules, or unsubscribe decisions
  3. Mailbox Breakdown: get_statistics(scope="mailbox_breakdown", mailbox="FolderName")

    • Shows: Total messages, unread count, read ratio
    • Use for: Identifying folders that need cleanup

Actionable Insights:

  • High email count from one sender → Create dedicated folder or filter
  • Many unread in Archive → Review and delete old emails
  • Flagged items accumulating → Schedule time to process

6. Bulk Cleanup Operations

Goal: Clean up old, unnecessary emails safely

Safe Cleanup Process:

  1. Identify Candidates: search_emails() with appropriate filters
  2. Review First: Always review what will be affected
  3. Move to Trash (reversible): manage_trash(action="move_to_trash")
  4. Verify: Check trash folder
  5. Permanent Delete (if certain): manage_trash(action="delete_permanent")
  6. Empty Trash (nuclear option): manage_trash(action="empty_trash")

Safety Considerations:

  • Always use max_deletes parameter (default: 5)
  • Review emails before permanent deletion
  • Consider exporting important mailboxes first: export_emails()

7. Draft Management Workflow

Goal: Manage email composition efficiently

Draft Workflow:

  1. Create Draft: When you need time to think

    manage_drafts(action="create", subject="...", to="...", body="...")
    
  2. List Drafts: Review pending drafts regularly

    manage_drafts(action="list")
    
  3. Send When Ready: Complete and send drafts

    manage_drafts(action="send", draft_subject="keyword")
    
  4. Clean Up: Delete outdated drafts

    manage_drafts(action="delete", draft_subject="keyword")
    

Best Practices:

  • Create drafts for emails needing careful wording
  • Review drafts weekly to avoid accumulation
  • Use descriptive subjects for easy draft identification

8. Thread Management

Goal: Handle email conversations effectively

Thread Strategies:

  1. View Full Thread: get_email_thread(subject_keyword="keyword")

    • Shows all related messages with Re:, Fwd: prefixes stripped
    • Sorted by date for chronological view
  2. Reply in Context: After viewing thread, reply with full context understanding

    • Use reply_to_all=True for group conversations
    • Use reply_to_all=False for one-on-one responses
  3. Archive Threads: Once resolved, move entire thread

    • Search for thread using subject
    • Move all messages to appropriate folder

Tool Selection Guidelines

When to use each tool:

GoalPrimary ToolAlternative
Get overviewget_inbox_overview-
Find specific emailget_email_with_contentsearch_emails
Advanced searchsearch_emails-
View conversationget_email_threadsearch_emails(subject_keyword)
Recent emailsget_recent_emailslist_inbox_emails
Organize emailsmove_email-
Bulk status updateupdate_email_status-
Reply/Composereply_to_email, compose_emailmanage_drafts
Analyticsget_statistics-
Cleanupmanage_trash-
Backupexport_emails-

Best Practices

Email Productivity

  1. Batch Processing: Process emails in dedicated time blocks, not continuously
  2. The 2-Minute Rule: If it takes less than 2 minutes, do it immediately
  3. Unsubscribe Aggressively: Use statistics to identify newsletter overload
  4. Folder Hierarchy: Keep folder structure simple (max 2-3 levels deep)
  5. Search, Don't Sort: For most emails, good search is better than complex folders

Tool Usage

  1. Safety Limits: Always respect max_moves, max_deletes parameters
  2. Confirm Destructive Actions: Always confirm before permanent deletion
  3. Use Filters: Combine filters (sender + subject + date) for precise searches
  4. Cross-Mailbox Search: Use mailbox="All" when location is uncertain
  5. Content Preview: Use include_content=True sparingly (slower but useful)

Organization Strategies

  1. Project-Based Folders: Organize by active projects, not vague categories
  2. Client Folders: Nested structure like "Clients/ClientName"
  3. Time-Based Archive: Archive folder with optional year subfolders
  4. Action Folders: "Action Required", "Waiting For", "Reference"
  5. Regular Cleanup: Archive or delete emails older than 30-90 days

Privacy & Security

  1. Check User Preferences: MCP tools inject user preferences - respect them
  2. Attachment Safety: Scan attachments before downloading
  3. Sensitive Data: Be cautious with export functions
  4. Account Selection: Always confirm which account to use for multi-account setups

Common Scenarios & Solutions

"I'm overwhelmed by my inbox"

  1. Start with get_inbox_overview() to see the scope
  2. Use get_statistics() to understand patterns
  3. Implement daily triage workflow (15-30 min/day)
  4. Unsubscribe from non-essential newsletters
  5. Set up basic folder structure
  6. Work toward inbox zero gradually (not all at once)

"I can't find an important email"

  1. Try get_email_with_content(subject_keyword) first
  2. If not found, use search_emails(mailbox="All", subject_keyword="..."))
  3. Try searching by sender: search_emails(sender="...")
  4. Try date range: search_emails(date_from="...", date_to="...")
  5. Check if it's in trash or other folders

"I need to organize emails by project"

  1. Review current structure: list_mailboxes()
  2. Create project folders using Mail app (MCP doesn't create folders)
  3. Search for project-related emails: search_emails(subject_keyword="ProjectName")
  4. Batch move: move_email(to_mailbox="Projects/ProjectName", max_moves=10)
  5. Use sender filters for team members

"I want to backup important emails"

  1. Export single important email: export_emails(scope="single_email", subject_keyword="...")
  2. Export entire mailbox: export_emails(scope="entire_mailbox", mailbox="Important")
  3. Choose format: txt (readable) or html (preserves formatting)
  4. Specify save location (default: ~/Desktop)

"Too many emails from one sender"

  1. Check statistics: get_statistics(scope="sender_stats", sender="...")
  2. If unwanted: Search and bulk delete/trash
  3. If wanted but overwhelming: Create dedicated folder and move all
  4. If newsletters: Consider unsubscribing (do in Mail app)

"I need to follow up on emails"

  1. Use flagging: update_email_status(action="flag", subject_keyword="...")
  2. Create "Follow Up" folder and move flagged items
  3. Review flagged emails weekly
  4. Clear flags when complete: update_email_status(action="unflag", ...)

Response Patterns

When user requests email help:

  1. Clarify Intent: Ask about their goal (organize, find, respond, cleanup)
  2. Get Context: Use get_inbox_overview() or relevant tool to understand situation
  3. Suggest Workflow: Propose appropriate workflow from this skill
  4. Execute with Confirmation: For destructive actions, confirm first
  5. Provide Tips: Share relevant best practices
  6. Offer Next Steps: Suggest related actions or maintenance routines

Error Handling

Common issues and solutions:

  • "Account not found": Check account name with list_accounts()
  • "Mailbox not found": Use list_mailboxes() to see available folders
  • "No emails found": Try broader search terms or mailbox="All"
  • Case sensitivity: Email searches are case-insensitive, but mailbox names might be
  • Safety limits hit: Increase max_moves/max_deletes if intentional, or process in batches

Integration with User Workflow

Always check for user preferences (injected in tool descriptions) and adapt suggestions:

  • Default account preferences
  • Preferred mailbox structure
  • Email volume tolerance
  • Organization philosophy (minimalist vs. detailed folders)

Remember

Email management is personal. Adapt these workflows to user preferences and working style. Focus on sustainable habits over perfect organization. The goal is productivity, not perfection.

FAQ

What does the email-management-expert skill do?

Expert email management assistant for Apple Mail. Use this when the user mentions inbox management, email organization, email triage, inbox zero, organizing emails, managing mail folders, email productivity, checking emails, or email workflow optimization. Provides intelligent workflows and best practices for efficient email handling.

How do I install email-management-expert?

Run npx skills add https://github.com/sundial-org/awesome-openclaw-skills --skill email-management-expert in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/email-management-expert/ (personal) or .claude/skills/email-management-expert/ (project).

Which AI agents can use email-management-expert?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is email-management-expert safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains email-management-expert?

It is published by sundial-org in sundial-org/awesome-openclaw-skills. It has 513 recorded installs.

More from sundial-org/awesome-openclaw-skills

View all →

stock-market-pro

sundial-org/awesome-openclaw-skills

Professional stock price tracking, fundamental analysis, and financial reporting tool. Supports global markets (US, KR, etc.), Crypto, and Forex with real-time data. (1) Real-time quotes, (2) Valuation metrics (PE, EPS, ROE), (3) Earnings calendar and consensus, (4) High-quality Candlestick & Line charts with technical indicators (MA5/20/60).

Business & Finance4.1K installs

ontology

sundial-org/awesome-openclaw-skills

Typed knowledge graph for structured agent memory and composable skills. Use when creating/querying entities (Person, Project, Task, Event, Document), linking related objects, enforcing constraints, planning multi-step actions as graph transformations, or when skills need to share state. Trigger on "remember", "what do I know about", "link X to Y", "show dependencies", entity CRUD, or cross-skill data access.

finance-news

sundial-org/awesome-openclaw-skills

Market news briefings with AI summaries. Use when asked about stock news, market updates, portfolio performance, morning/evening briefings, financial headlines, or price alerts. Supports US/Europe/Japan markets, WhatsApp delivery, and English/German output.

Business & Finance2.8K installs

exa-web-search-free

sundial-org/awesome-openclaw-skills

Free AI search via Exa MCP. Web search for news/info, code search for docs/examples from GitHub/StackOverflow, company research for business intel. No API key needed.

memory-setup

sundial-org/awesome-openclaw-skills

Enable and configure Moltbot/Clawdbot memory search for persistent context. Use when setting up memory, fixing "goldfish brain," or helping users configure memorySearch in their config. Covers MEMORY.md, daily logs, and vector search setup.

1.7K installs

ffmpeg-video-editor

sundial-org/awesome-openclaw-skills

Generate FFmpeg commands from natural language video editing requests - cut, trim, convert, compress, change aspect ratio, extract audio, and more.

Media & Creative1.6K installs

Popular productivity & automation skills

View category →

agent-browser

vercel-labs/agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.

OfficialProductivity & Automation1.3M installs

lark-doc

open.feishu.cn

飞书云文档(Docx / Wiki)内容操作:读取、创建、编辑文档,插入或下载图片附件,以及操作思维笔记。用户提供文档 URL/token(包括 doubao.com 的 /docx/、/wiki/)时使用;按 URL 路径/token 而非域名路由;/page/ 是妙搭应用,非飞书云文档。文档内嵌资源按读取参考中的统一规则分流。独立评论操作走 lark-drive;随正文读取评论使用 docs +fetch。表格或 Base 内部数据操作不在本 skill。

lark-base

open.feishu.cn

飞书多维表格(Base)操作:建表、字段、记录、视图、统计、公式/lookup、表单、仪表盘、应用模式(BaseApp/AppMode 页面与组件)、Workspace 目录、workflow、角色权限、模板中心(多维表格模板分类/列表/搜索);遇到 Base/多维表格/bitable、BaseApp/AppMode、/base/ 或 /app/ 链接时使用。BaseApp 不走 lark-apps;文件导入/导出转 lark-drive,认证/授权转 lark-shared。

lark-drive

open.feishu.cn

飞书云空间(云盘/云存储):管理 Drive 文件和文件夹,包含上传/下载、创建文件夹、复制/移动/删除、查看元数据、查询权限设置、评论/权限/订阅、标题、版本、飞书文档密级标签(secure labels)和本地文件导入。用户需要整理云盘目录、处理云空间资源 URL/token、判断链接类型/真实 token/标题,或导入 Word/Markdown/Excel/CSV/PPTX/.base 为 docx/sheet/bitable/slides 时使用;doubao.com 云空间 URL/token 也按资源路径和 token 路由,不回退 WebFetch。不负责:文档内容编辑(走 lark-doc)、表格/Base 表内数据操作(走 lark-sheets/lark-base)、知识空间节点/成员管理(走 lark-wiki)、原生 Markdown 文件读写/patch/diff(走 lark-markdown)。

lark-shared

open.feishu.cn

Use for lark-cli setup/auth tasks: auth login/status/logout, user vs bot identity, business-domain permissions (--domain, including all/docs/drive), missing scopes, revoking authorization, or handling notice JSON.

lark-im

open.feishu.cn

飞书即时通讯:收发消息和管理群聊。发送和回复消息、搜索聊天记录、管理群聊成员、上传下载图片和文件、管理表情回复、发送应用内/短信/电话加急、发送和处理交互卡片(Interactive Card)、监听卡片按钮回调(card.action.trigger)。当用户需要发消息、查看或搜索聊天记录、下载聊天中的文件、查看群成员、搜索群、创建群聊或话题群、管理标记数据、管理 Feed 置顶(添加/移除/查询置顶会话)、管理标签数据、处理卡片回调时使用。