dingtalk-mail

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

钉钉邮箱 Skill

DingTalk Email Skill

前置条件 — 执行操作前必读

Prerequisites — Read before performing any operation

**CRITICAL — 执行任何
dws
操作前,MUST 先用 Read 工具完整读取
dingtalk-shared
。**该轻量文件包含全局执行契约、安全底线及 shared references 的按需加载导航;不要预加载其全部 references。
命令参考:mail.md。复杂搜索、附件、批量处理、草稿等多步邮件场景参考:09-mail.md。
<!-- VISIBLE_SHORTCUTS_START -->
CRITICAL — Before executing any
dws
operation, you MUST first use the Read tool to fully read
dingtalk-shared
.
This lightweight file contains the global execution contract, security baseline, and on-demand loading navigation for shared references; do not pre-load all its references.
Command reference: mail.md. For multi-step email scenarios such as complex search, attachments, batch processing, drafts, see: 09-mail.md.
<!-- VISIBLE_SHORTCUTS_START -->

Shortcuts(无专用脚本/recipe 时优先)

Shortcuts (preferred when no dedicated script/recipe exists)

以下 shortcut 同时进入公开 catalog 与 Runtime Schema。按本 skill/recipe 路由,命中时 Shortcut 优先于原子命令。参数只查
dws schema --cli-path "mail +<shortcut>" --compact --jq '{cli_path,parameters,constraints,confirmation}' -f json
;仅需且已发布
result
时查
--jq '{cli_path,outcomes:.result.outcomes,pagination}'
,字段级再查
data_schema
;缺失不以 Help/样例推断。Schema 不可用才读一次已知 leaf Help;
unknown flag
用同 leaf Help 修正一次。
unknown command
禁 Help:错误 suggestion → 已加载 Skill/reference 明确入口;均无则报漂移。禁全 Catalog/root/parent/product Help;仅映射、接口或 provenance 审计省略
--compact
。现有路由和 reference 均无法定位低频能力时,才用
dws shortcut list --service mail --format json
发现。
Shortcut风险适用场景
dws mail +find-mail-user
read按关键词搜索邮箱联系人并投影列表(姓名/昵称/邮箱/工号等)
dws mail +folder-list
read列出顶层文件夹或指定父文件夹下的子文件夹
dws mail +message
read读取一封邮件的完整正文与附件元数据
dws mail +messages
read按请求顺序读取多封邮件并逐封验证身份
dws mail +search-mail
read按 KQL 关键词搜索邮件并投影列表(主题/发件人/时间/messageId)
dws mail +thread
read读取完整邮件会话并精确验证 conversationId
dws mail +triage
read列出或筛选邮件摘要,自动解析邮箱与收件箱
dws mail +user-search
read按关键词或工号搜索邮箱用户(仅企业邮箱)
<!-- VISIBLE_SHORTCUTS_END -->
The following shortcuts enter both the public catalog and Runtime Schema. Route according to this skill/recipe; when matched, Shortcuts take precedence over atomic commands. For parameters, only query
dws schema --cli-path "mail +<shortcut>" --compact --jq '{cli_path,parameters,constraints,confirmation}' -f json
; when only the published
result
is needed, query
--jq '{cli_path,outcomes:.result.outcomes,pagination}'
, and for field-level details query
data_schema
; do not infer missing parts from Help or examples. Only read a known leaf Help once when the Schema is unavailable; fix an
unknown flag
once with the same leaf Help.
unknown command
forbids Help: wrong suggestion → use the explicit entry in the loaded Skill/reference; if neither exists, report drift. Forbid full Catalog/root/parent/product Help; omit
--compact
only for mapping, interface, or provenance audits. When existing routes and references cannot locate a low-frequency capability, use
dws shortcut list --service mail --format json
to discover.
ShortcutRiskUse case
dws mail +find-mail-user
readSearch email contacts by keyword and project a list (name/nickname/email/employee ID, etc.)
dws mail +folder-list
readList top-level folders or subfolders under a specified parent folder
dws mail +message
readRead the full body and attachment metadata of one email
dws mail +messages
readRead multiple emails in the requested order and verify identity one by one
dws mail +search-mail
readSearch emails by KQL keywords and project a list (subject/sender/time/messageId)
dws mail +thread
readRead the full email conversation and precisely verify conversationId
dws mail +triage
readList or filter email summaries, automatically resolve mailbox and inbox
dws mail +user-search
readSearch mailbox users by keyword or employee ID (enterprise mailbox only)
<!-- VISIBLE_SHORTCUTS_END -->

意图表

Intent Table

用户说命令
"发邮件给 a@b.com"
dws mail mailbox list --format json
→
dws mail message send --from <邮箱> --to a@b.com --subject "<标题>" --content "<正文>" --format json
"回复 / 全部回复 / 转发"
dws mail message reply
/
reply-all
/
forward
"今天未读邮件"
python scripts/mail_unread_summary.py
"带抄送发送"
python scripts/mail_send_with_cc.py --to a@b.com --cc c@d.com --subject "<标题>" --body "<正文>"
User saysCommand
"Send email to a@b.com"
dws mail mailbox list --format json
→
dws mail message send --from <mailbox> --to a@b.com --subject "<subject>" --content "<body>" --format json
"Reply / Reply all / Forward"
dws mail message reply
/
reply-all
/
forward
"Today's unread emails"
python scripts/mail_unread_summary.py
"Send with CC"
python scripts/mail_send_with_cc.py --to a@b.com --cc c@d.com --subject "<subject>" --body "<body>"

标准 SOP(必遵流程)

Standard SOP (Mandatory Process)

命中以下意图必须按对应 SOP 顺序执行;禁止跳步、替换命令、编造 email/messageId。每条命令必须带
--format json
。收件邮箱必须真实解析,禁止猜测。
When the following intents are matched, you must execute them in the corresponding SOP order; do not skip steps, replace commands, or fabricate email/messageId. Every command must include
--format json
. The recipient mailbox must be actually resolved; do not guess.

SOP-1 拿邮箱(get-mailbox)

SOP-1 Get Mailbox (get-mailbox)

触发:我的邮箱/发件需要邮箱/查邮件需要邮箱。
  1. 执行(必须):
    dws mail mailbox list --format json
    ,取自己的
    email
    (默认选企业邮箱
    type:ORG
    );查他人邮箱用
    dws mail user search --keyword "<姓名>" --format json
    ,禁止用
    mailbox list
    查他人。
禁止:把
mailbox list
当作他人邮箱查询、猜测邮箱地址。
Trigger: my mailbox / sending needs a mailbox / checking email needs a mailbox.
  1. Execute (required):
    dws mail mailbox list --format json
    , get your own
    email
    (default to enterprise mailbox
    type:ORG
    ); use
    dws mail user search --keyword "<name>" --format json
    to look up other users' mailboxes; do not use
    mailbox list
    to look up others.
Forbidden: use
mailbox list
as a query for others' mailboxes, or guess email addresses.

SOP-2 查 / 搜邮件(search-mail)

SOP-2 View / Search Email (search-mail)

触发:查邮件/搜邮件/某主题邮件/某人发的邮件。
  1. 拿邮箱(必须):先按 SOP-1 取
    email
    ;用户已明确提供可跳过。
  2. 执行(必须):浏览文件夹
    dws mail message list --email <邮箱> --limit <n> --format json
    ;KQL 搜索
    dws mail message search --email <邮箱> --query "<KQL>" --limit 20 --format json
    (KQL 如
    subject:周报
    、
    from:alice@x.com
    、
    folderId:2
    、
    hasAttachments:true
    ,只通过
    --query
    传
    )。
  3. 取正文(必须):
    dws mail message get --email <邮箱> --id <messageId> --format json
    ;
    messageId
    从列表/搜索结果取,禁止编造。
禁止:把 KQL 拆成多个 flag、跳过
message list/search
直接猜 messageId。
Trigger: view emails / search emails / emails on a topic / emails from someone.
  1. Get mailbox (required): first obtain
    email
    per SOP-1; may skip if the user explicitly provided it.
  2. Execute (required): browse folders
    dws mail message list --email <mailbox> --limit <n> --format json
    ; KQL search
    dws mail message search --email <mailbox> --query "<KQL>" --limit 20 --format json
    (KQL examples:
    subject:weekly report
    ,
    from:alice@x.com
    ,
    folderId:2
    ,
    hasAttachments:true
    ; only pass via
    --query
    ).
  3. Get body (required):
    dws mail message get --email <mailbox> --id <messageId> --format json
    ; take
    messageId
    from the list/search results, do not fabricate.
Forbidden: split KQL into multiple flags, skip
message list/search
and guess messageId directly.

SOP-3 发邮件(send-mail)

SOP-3 Send Email (send-mail)

触发:发邮件/写邮件/群发。
  1. 发件邮箱(必须):
    dws mail mailbox list
    取自己邮箱。
  2. 收件邮箱(必须):地址直接用;姓名按 mail.md "查找他人邮箱地址"流程(
    mail user search
    等)获取,禁止猜测。
  3. 执行(必须):
    dws mail message send --from <发件邮箱> --to <收件邮箱> --subject "<主题>" --content "<正文>" --format json
    ;按需
    --cc
    /
    --attachment
    /
    --inline-attachment
    。
  4. 验证(必须):从发送返回取真实
    internetMessageId
    ,执行
    dws mail message verify --email <发件邮箱> --internet-message-id <internetMessageId> --format json
    查发送状态;不要把普通
    messageId
    传给 verify。
禁止:猜测收件邮箱、发送后不确认状态就答复"已发送"。
Trigger: send email / write email / mass send.
  1. Sender mailbox (required): get your own mailbox via
    dws mail mailbox list
    .
  2. Recipient mailbox (required): use the address directly; for names, obtain the address per the "find other's email address" flow in mail.md (via
    mail user search
    etc.); do not guess.
  3. Execute (required):
    dws mail message send --from <sender mailbox> --to <recipient mailbox> --subject "<subject>" --content "<body>" --format json
    ; add
    --cc
    /
    --attachment
    /
    --inline-attachment
    as needed.
  4. Verify (required): get the real
    internetMessageId
    from the send response, run
    dws mail message verify --email <sender mailbox> --internet-message-id <internetMessageId> --format json
    to check the sending status; do not pass a normal
    messageId
    to verify.
Forbidden: guess the recipient mailbox, or reply "sent" without confirming the status after sending.

SOP-4 回复 / 转发(reply-forward)

SOP-4 Reply / Forward (reply-forward)

触发:回复邮件/回复全部/转发。
  1. 拿邮箱 + 原邮件(必须):SOP-1 取邮箱;用户未给
    messageId
    时必须先走 SOP-2 定位原邮件
    messageId
    。
  2. 执行(必须):回复
    dws mail message reply --from <邮箱> --id <messageId> --content "<正文>" --format json
    ;回复全部用
    reply-all
    ;转发
    dws mail message forward --from <邮箱> --to <收件邮箱> --id <messageId> --content "<附言>" --format json
    。
禁止:未定位原邮件就回复/转发、编造 messageId。
Trigger: reply to email / reply all / forward.
  1. Get mailbox + original email (required): get mailbox via SOP-1; if the user did not provide a
    messageId
    , you must first locate the original email's
    messageId
    via SOP-2.
  2. Execute (required): reply
    dws mail message reply --from <mailbox> --id <messageId> --content "<body>" --format json
    ; use
    reply-all
    for reply all; forward
    dws mail message forward --from <mailbox> --to <recipient mailbox> --id <messageId> --content "<note>" --format json
    .
Forbidden: reply/forward without locating the original email, or fabricate messageId.

高频硬约束

High-Frequency Hard Constraints

  • 用户要"完整内容/看看这封邮件/正文"时,
    message search
    命中后必须继续调用
    dws mail message get --email <邮箱> --id <messageId> --format json
    ;不要只列候选后停下。
  • 搜到多封邮件时,若用户给了明确主题、附件名、发件人或时间线索,先选最匹配的一封执行
    message get
    ;只有同等候选无法判断时才询问用户。
  • 附件链路固定三步:
    message search
    →
    attachment list --email <邮箱> --id <messageId>
    →
    attachment download --email <邮箱> --message-id <messageId> --attachment-id <attachmentId> --name <文件名>
    ;不存在批量下载命令。
  • 写入类操作(发送、回复、转发、删除、批量移动)按安全策略确认;只读查看、搜索、附件列表、下载不需要确认。
  • 所有
    dws mail
    命令加
    --format json
    ,并复用同一封邮件的
    messageId
    ,不要重新搜索导致目标漂移。
  • When the user asks for "full content / view this email / body", after a
    message search
    hit you must continue to call
    dws mail message get --email <mailbox> --id <messageId> --format json
    ; do not stop after listing candidates.
  • When multiple emails are found, if the user gave a clear subject, attachment name, sender, or time clue, first select the best match and run
    message get
    ; only ask the user when equally matching candidates cannot be distinguished.
  • The attachment chain is fixed in three steps:
    message search
    →
    attachment list --email <mailbox> --id <messageId>
    →
    attachment download --email <mailbox> --message-id <messageId> --attachment-id <attachmentId> --name <filename>
    ; there is no batch download command.
  • Write operations (send, reply, forward, delete, batch move) require confirmation per security policy; read-only views, searches, attachment listings, and downloads do not require confirmation.
  • Add
    --format json
    to all
    dws mail
    commands, and reuse the same email's
    messageId
    ; do not re-search causing target drift.

轨迹高频直达规则

High-Frequency Direct Access Rules

  • 已被本页或
    09-mail.md
    精确覆盖的命令,直接执行;不要先探测
    contact
    、
    api
    、
    auth
    、
    profile
    、Help 或 Schema。仅在命令真实报参数错误后,读取该命令的 leaf Help 一次。
  • 多条件 KQL 必须用显式
    AND
    ,例如收件箱附件邮件:
    hasAttachments:true AND folderId:2
    ;不要把相邻条件当作隐式 AND。
  • 用户只要首个或任一单附件时,初始搜索后按相关性最多检查 3 个候选的
    attachment list
    ,下载命中附件并做一次本地存在性/大小检查后停止;若均未命中,只能说明已检查范围并询问是否继续翻页,不能断言不存在。用户要求全部/批量附件时,遍历全部匹配页和邮件,再逐个下载每个附件。
  • “创建邮箱联系人”属于邮箱个人通讯录,固定走
    dws mail contact create/list
    ,不要切到
    dingtalk-contact
    。只有“按人名解析邮件收件地址”才走下方跨产品协作。
  • 用户要求用当前时间生成唯一标题且未指定显示格式时,使用紧凑格式
    date +%H%M%S
    ;只有用户明确要求
    HH:mm:ss
    等格式时才原样保留。
  • 批量删除邮件或将整会话移入已删除前,先展示精确目标和不含确认参数的命令预览并停止;用户明确确认后,执行流程仅对同一组参数追加
    --yes
    。操作成功后只做一次针对原 ID 或唯一主题的回读,结果符合预期即停止。
  • 创建类返回了
    messageId
    、
    contactId
    或
    internetMessageId
    时,后续直接复用返回 ID;不要为了重新定位目标而做宽泛 list/search。
  • 一次精确回读已经证明目标状态后结束任务;若回读冲突,报告冲突和已执行命令,不扩大到低层 API 或其他产品继续试探。
  • For commands precisely covered by this page or
    09-mail.md
    , execute directly; do not first probe
    contact
    ,
    api
    ,
    auth
    ,
    profile
    , Help, or Schema. Only after the command actually reports a parameter error, read that command's leaf Help once.
  • Multi-condition KQL must use explicit
    AND
    , e.g., inbox emails with attachments:
    hasAttachments:true AND folderId:2
    ; do not treat adjacent conditions as implicit AND.
  • When the user only wants the first or any single attachment, after the initial search check at most 3 candidates'
    attachment list
    by relevance, download the hit attachment, do a local existence/size check, then stop; if none hit, only state the checked scope and ask whether to continue paging; do not assert it does not exist. When the user asks for all/batch attachments, traverse all matching pages and emails, then download each attachment one by one.
  • "Create mailbox contact" belongs to the mailbox personal address book; always use
    dws mail contact create/list
    , do not switch to
    dingtalk-contact
    . Only "resolve email recipient address by person name" uses the cross-product collaboration below.
  • When the user requires generating a unique title with the current time and no display format is specified, use the compact format
    date +%H%M%S
    ; only preserve formats like
    HH:mm:ss
    when the user explicitly requests them.
  • Before batch-deleting emails or moving an entire conversation to deleted, first show the precise targets and a command preview without the confirmation parameter, then stop; after the user explicitly confirms, the execution flow appends
    --yes
    to the same set of parameters only. After the operation succeeds, do a single readback targeting the original ID or unique subject; stop when the result matches expectations.
  • When a create-type operation returns
    messageId
    ,
    contactId
    , or
    internetMessageId
    , subsequently reuse the returned ID directly; do not do broad list/search to re-locate the target.
  • End the task after one precise readback has proven the target state; if the readback conflicts, report the conflict and executed commands; do not expand to lower-level APIs or other products to continue probing.

跨产品协作

Cross-Product Collaboration

  • 收件人是人名 → 先用
    dingtalk-contact
    取
    orgAuthEmail
  • 钉钉内消息 → 切到
    dingtalk-chat
  • Recipient is a person name → first use
    dingtalk-contact
    to get
    orgAuthEmail
  • DingTalk internal messages → switch to
    dingtalk-chat

局部意图与短流程

Local Intents and Mini-Flows

  • 局部意图消歧;短流程。
  • Local intent disambiguation; mini-flows.