菜单
Send and read email through the mosadd OS module mp0st. Every mosadd user has a personal address `<userId>@mosadd.com` — outgoing mail flows through the mosadd mp0st pipeline. Use when the user asks to send an email or read a message by id.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Send, list, and respond to direct messages on mosadd. Use when the user wants to message a mosadd contact, check their inbox, or accept/reject a contact request. Multi-thread per contact is the USP — each contact can have multiple named threads (unlike WhatsApp/Telegram).
Manage persistent channels on mosadd — Discord/Slack-style spaces with members, roles, and capabilities (text, push-to-talk, live streams). Use when the user wants to create, list, get details on, update, or delete a long-lived channel.
Coordinate with other AI agents across tools and sessions over one shared mosadd channel. Use when you are one of several agents (Claude Code, Cursor, Antigravity, Windsurf, or separate sessions) working on the same project — post what you're doing, hand off work, flag that you need a human, and read what the other agents already did. Turns isolated agent silos into one human-visible coordination channel.
Search and reason over the user's own mosadd messages, emails, calls, and notes via the RAG knowledge base. Use when the user asks "what did <X> say about <Y>", "summarize my conversations about <topic>", "find emails about <thing>", or "ingest these documents into my knowledge base". NOT for searching the public web (that's a different tool) — mRAG is grounded strictly in the user's indexed mosadd data.
Push-to-talk voice rooms on mosadd. Half-duplex floor control — one speaker at a time, FIFO queue, anti-hog auto-release. Use when the user wants a walkie-talkie style room, "open a PTT channel", join an ops/field-team room, or hold the floor to speak. NOT for full-duplex 1:1 voice (that's mDM_call_start).
| name | mosadd-mail |
| description | Send and read email through the mosadd OS module mp0st. Every mosadd user has a personal address `<userId>@mosadd.com` — outgoing mail flows through the mosadd mp0st pipeline. Use when the user asks to send an email or read a message by id. |
This skill operates the mp0st OS module of mosadd. Every mosadd user gets <userId>@mosadd.com as a built-in address — no separate email provider needed.
| Tool | Use it for |
|---|---|
mp0st_send | Send mail from <userId>@mosadd.com. Supports body_text/body_html, cc/bcc, reply_to, plus monitoring/legal options: tracking, force_reader, watermark, disclose_tracking, auto_destruct. |
mp0st_list | List the user's mailbox newest-first; filter by direction (inbound/outbound); page with before + next_cursor. |
mp0st_view | Read the full body + metadata of one email by message_id. |
mp0st_delete | Soft-delete one of the user's emails by message_id. |
mp0st_stats | Engagement summary for one sent email: opens, unique opens, clicks, likely-forwarded, first/last open. |
mp0st_events | Raw per-event engagement timeline for one email (opens, clicks, forwards, reader signals) with timestamps. |
mp0st_metrics | Mailbox-wide aggregate across all sent mail: total sent, open rate, total opens/clicks, forwarded. |
mp0st_revoke | Recall a sent email's secure-reader access (restore:true to re-enable). Cannot claw back already-read content. |
mp0st_audit_export | Tamper-evident HMAC-signed engagement audit report for one email (legal/compliance). |
mp0st_consent | Manage recipient tracking opt-outs (GDPR/ePrivacy): list / check / optin. |
mp0st_notify | Recent engagement feed across all sent mail ("who just opened/clicked"); poll with since/cursor. |
mp0st_send_as_agent | Send mail attributed to the AGENT (stamps sent_by='agent' + agent_id/task_id). Needs MOSADD_API_KEY (hub claim). |
Trigger on these user intents:
mp0st_sendmp0st_list (filter direction)mp0st_viewmp0st_deletemp0st_stats (summary) or mp0st_events (per-event detail)mp0st_metricsmp0st_notifymp0st_revokemp0st_audit_exportmp0st_consentmp0st_send_as_agentPick body format. Default to body_text for short messages. Use body_html when the user explicitly wants formatting (links, lists, images). Both can be present.
Multiple recipients. to accepts either a single email or an array (up to 50). Use cc / bcc for the obvious roles.
Reply-to. If the user wants replies routed somewhere else (e.g. an alias), pass reply_to. Otherwise replies go to the user's <userId>@mosadd.com.
Subjects. Match the user's tone. Don't add a subject they didn't ask for. RFC 5322 caps at 998 chars — clip if needed.
User: "Send Alice an email with subject 'Quote for project X' and body 'Hi Alice, attached is the quote. Best, M.'"
You:
mp0st_send({ to: "alice@example.com", subject: "Quote for project X", body_text: "Hi Alice, attached is the quote. Best, M." })→{ message_id, status, is_internal }- Reply: "Sent to alice@example.com. You can check opens/clicks later with
mp0st_stats."
Outbound delivery uses Resend by default in alpha. The mosadd hub will broker BYOK Resend / Mailgun / SendGrid in Phase 2 — for now the user's mosadd Supabase backend handles routing transparently.
mDM_send.mDM_send (the user almost always wants the chat module).force_reader, watermark, auto_destruct) unless the user asks — and prefer disclose_tracking for GDPR/ePrivacy compliance when tracking is on.