菜单
How agents read from and write to Outlook via Microsoft Graph. Composer uses it to save Drafts. Cadence uses it to detect sends and replies. Read-only patterns work today via the M365 MCP; write paths are stubbed until a Graph write MCP or a small helper is wired.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
When to follow up, what to send, and when to stop. Defines pre-approved templated cadence steps that the Cadence agent can auto-fire under guardrails. Used by the Cadence agent.
Compliance and content checks that gate every outbound send. Used by the Composer (pre-draft) and the Cadence agent (pre-send).
The canonical list of kill switches every agent checks at the top of every loop tick. If any trigger is active, the agent stops the relevant work.
How to research a prospect end-to-end — pull profile, pull company, surface recent signals, score ICP fit, write a dossier. Used by the Prospector agent.
How to write outbound messages in the Synozur firm voice. Used by the Composer agent. Anchored on a Voice DNA artifact extracted from real best-performing messages.
The markdown file schema for prospects. One file per lead at $PROSPECT_DIR/<slug>.md. Source of truth for state, dossier, drafts, conversation, and audit log. Read and written by all three agents.
| name | outlook-ops |
| description | How agents read from and write to Outlook via Microsoft Graph. Composer uses it to save Drafts. Cadence uses it to detect sends and replies. Read-only patterns work today via the M365 MCP; write paths are stubbed until a Graph write MCP or a small helper is wired. |
The session's M365 MCP exposes these read operations:
outlook_email_search — search the user's mailbox by query
(sender, recipient, subject, body, date range)outlook_calendar_search — read calendar eventsfind_meeting_availability — find free/busy slotssharepoint_search / sharepoint_folder_search — surface existing
Synozur intelThe Cadence agent uses these to:
The current MCP set has no outlook_send_mail or outlook_save_draft
tool. Until one is wired, the Composer's "save to Outlook Drafts" step
runs via one of three options (v1 supports option C):
Option A — Graph SDK helper script. Add a small Python helper at
tools/outlook_draft.py that authenticates to Graph (delegated auth,
the user's signed-in identity) and creates a draft via
POST /me/messages with a JSON body containing subject, body, and
toRecipients. Messages created via this endpoint default to draft
state (the isDraft flag is set true by Graph until the message is
explicitly sent). The Composer invokes the helper via a tool wrapper.
Requires app registration in the Synozur tenant with Mail.ReadWrite.
Option B — A write-side MCP. Wire a Graph MCP server (e.g. an
internal Synozur MCP or one of the community Graph MCPs) into the
session's MCP config. The Composer then calls
mcp__graph__save_draft({to, subject, body}). Cleanest long-term path.
Option C — Human bridge (v1 default). The Composer writes the
draft to the prospect MD file under ## Draft (pending approval). A
tiny tools/sync_drafts.py script (the operator runs it manually or on
a cron) walks the prospect directory, finds any ## Draft (pending approval) sections not yet in Outlook, and creates the Draft via the
Graph SDK using the operator's authenticated session. The Composer
itself does not write to Outlook.
For first-generation v1, use Option C. It removes the agent's write authority over Outlook entirely. The agent writes markdown; a sync script materializes markdown into Drafts.
When the Composer writes the ## Draft (pending approval) section, it
must use this exact structure so the sync script can parse it:
## Draft (pending approval) — <ISO 8601 timestamp>
**Channel:** email
**To:** <email>
**Subject:** <subject>
<body — plain text, no markdown, no signature; the sync script appends
the signature configured in the operator's Outlook>
---
**Reasoning trace:**
- ...
The sync script reads from **To:** through to the --- divider. The
reasoning trace is for humans and stays in the MD file only.
outlook_email_search:
folder: sent-items
to: <recipient email>
subject: <draft subject>
after: <draft timestamp>
If exactly one match → mark sent with sent_at: <message timestamp>
and thread_id: <conversationId from the result>.
If zero matches and the draft is older than 7 days → set
hold_reason: draft never sent, do not transition.
If multiple matches → take the most recent and log a warning.
outlook_email_search:
folder: inbox
conversationId: <thread_id from the lead>
from: <prospect email>
after: <sent_at from the lead>
If a match → transition to state: replied, copy the reply body into
the lead's ## Conversation section, classify with the Composer per
skills/cadence-rules/.
All Graph access is delegated, using the operator's M365 sign-in. The agent does not hold a service-principal token. This intentionally caps blast radius: if the harness goes wrong, it can only do what the signed-in user could already do, and the audit shows it under that user.