Agent Skills
› fanfan-de/anybox
› outlook-email-shared-mailboxes
outlook-email-shared-mailboxes
GitHub处理委托或共享 Outlook 邮箱的操作，包括读取、发送（代发）、标记状态及移动邮件。需指定精确的 UPN，区分于用户主邮箱操作，确保权限与数据隔离安全。
Trigger Scenarios
用户要求查看共享/委托邮箱内容
用户要求以共享邮箱名义发送邮件
用户要求管理共享邮箱中的文件夹或邮件状态
Install
npx skills add fanfan-de/anybox --skill outlook-email-shared-mailboxes -g -y
SKILL.md
Frontmatter
{
"name": "outlook-email-shared-mailboxes",
"description": "Work with delegated or shared Outlook Email mailboxes. Use when the user explicitly wants to read another mailbox, send from or on behalf of a shared mailbox, mark shared mail read or unread, move shared mail, or browse folders in a shared mailbox."
}
Outlook Email Shared Mailboxes
Use this skill only when the user is working with a delegated or shared Outlook mailbox. These actions are separate from signed-in-user mailbox actions on purpose.
Required Target
- Require the exact delegated/shared mailbox owner email address or UPN before reading or writing shared mail.
- Pass that identity as
mailbox_user_principal_name. - Do not discover, infer, or guess mailbox identities from display names alone.
Action Routing
- Read signed-in user's mailbox: use the base Outlook Email skill, not this workflow.
- Read shared mailbox messages:
list_shared_messages. - Browse shared mailbox folders:
list_shared_mail_folders. - Fetch one shared mailbox message:
fetch_shared_message. - Send a new plain-text email from or on behalf of the shared mailbox:
send_email_on_behalf. - Mark shared mail read or unread:
mark_shared_email_read_state. - Move shared mail:
move_shared_email.
Workflow
- Confirm the mailbox target and preserve the exact
mailbox_user_principal_name. - For folder-specific work, list shared folders first and use exact folder IDs instead of guessing folder paths.
- For message reads, keep the shared mailbox target attached to every message ID. A message ID from a shared mailbox should later be fetched or mutated with the corresponding shared action.
- For sends, drafts, moves, and read-state changes, say which mailbox is being used before performing the write.
- If the user shifts from a shared mailbox to their own mailbox, switch back to the signed-in-user actions.
Safety
- Treat
send_email_on_behalfas high impact. It sends immediately from another mailbox and supports plain text only. - Do not use
send_emailwhen the user said to send from a shared mailbox. - Do not use
move_emailormark_email_read_stateon message IDs obtained from shared mailbox actions. - If a write fails because shared/delegated scopes are unavailable, say the shared-mailbox action or scope is the blocker rather than claiming the normal mailbox action cannot work.
Example Requests
- "List unread mail in the support shared mailbox support@example.com."
- "Send this status note from ops-notices@example.com to the incident responders."
- "Move that message in the billing shared mailbox to its Escalations folder."
Version History
- 08dc189 Current 2026-07-05 19:04
