local-mcp-email-to-action
Use when the user wants to deal with their inbox — find what needs a response, draft replies, and turn emails into calendar events or reminders. Captures the common email→read→reply→schedule workflow on macOS (Apple Mail, Calendar, Reminders). Powered by LMCP.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-14
- Stars
- ★ 1.6k
- Forks
- 491
01 前言 Front Matter
- name
- local-mcp-email-to-action
- description
- Use when the user wants to deal with their inbox — find what needs a response, draft replies, and turn emails into calendar events or reminders. Captures the common email→read→reply→schedule workflow on macOS (Apple Mail, Calendar, Reminders). Powered by LMCP.
03 SKILL.md 正文
Inbox to action
Telemetry shows users don't just read email — they turn it into action: read → reply → schedule a meeting or create a reminder. This skill codifies that end-to-end flow. Every tool below works with Apple Mail, Calendar and Reminders, so the flow runs only on macOS.
The flow
- Surface what needs attention —
search_emails/list_emails(setaccount=to stay fast), thenread_emailon the ones that matter. Summarize: who, what they want, urgency. - Reply —
create_draft(withreply_to_message_idfor replies). Compose the draft; the user reviews and sends it. Never auto-send. - Turn the email into action when it implies one:
- A meeting request →
create_calendar_event(confirm calendar + exact times first). - A task/follow-up →
create_reminder(with a due date if the email implies one).
- A meeting request →
Good practice
- Batch: skim the inbox, group into "needs reply", "schedule this", "just FYI".
- For each "needs reply", draft a concise response in the user's voice; show it before saving.
- When an email says "let's meet Tuesday", propose a concrete slot (check
list_calendar_eventsfor conflicts) and create the event on confirmation. - Destructive/outgoing steps are preview-first: show the draft / the event, confirm, then apply.
- Keep the user in control — propose, don't auto-execute sends or deletes.
04 同仓库更多 Skills
worktable-review-with-annotations
Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.
worktable-find-and-synthesize-context
Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.
worktable-create-or-update-docs
Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.
worktable-create-or-manage-records
Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.
worktable-create-or-manage-interactive-html
Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.
worktable-collaborate-threads
Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.