Content
81%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A strong, highly actionable instruction-only skill: concrete tool modes and parameters, four well-sequenced workflows with explicit user-confirmation validation for every destructive or batch operation, and a common-errors checklist. Its main weakness is moderate padding — the 'why' rationale paragraphs re-explain email irreversibility and threading mechanics Claude already knows, and the quick-reference section duplicates the tool table.
Suggestions
Trim the '第 5 步为什么必须做' and '第 6 步为什么必须带 inReplyTo' rationale paragraphs to one-line imperatives (e.g., '邮件发出不可撤回——必须先展示草稿并等待确认' and 'inReplyTo 填原邮件 messageId，references 填原邮件 references 链 + messageId，否则线程断裂'), removing the explanation of how Gmail/Outlook/Apple Mail organize conversations.
Remove the '操作速查' section's mode/action lists since they duplicate the '工具清单' table, or merge the two into one section.
In 流程三, make the per-batch checkpoint concrete by specifying the report format (e.g., '每批操作后报告成功/失败条数与剩余数量') so progress reporting is verifiable rather than implied.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly tight (tool table, mode-selection map, numbered workflows), but the 'why' rationale paragraphs are unnecessary — '因为邮件一旦发出就无法撤回。发错人、写错内容可能造成不可逆的尴尬甚至商业损失' and the explanation that '所有主流邮件客户端（Gmail、Outlook、Apple Mail）都依赖 Message-ID 头来组织会话' cover concepts Claude already knows. The '操作速查' section also re-lists the same 7 modes and 8 actions already tabulated at the top. | 3 / 5 |
Actionability | Guidance is fully executable: exact tool modes with required parameters ('get-message (需要 messageId)', 'list-messages (需要 accountEmail + mailbox)'), concrete pagination values ('pageSize: 20', 'cursor + pageSize(1-50)'), specific send parameters ('需要 accountEmail、to、subject、bodyText；回复额外需要 inReplyTo、references'), and concrete forwarding construction ('subject 加 Fwd: 前缀，bodyText 包含 ---------- Forwarded message ---------- 分隔头'). Exact tool schemas are appropriately deferred via ToolSearch. | 5 / 5 |
Workflow Clarity | Four workflows are clearly sequenced with explicit validation checkpoints: '⚠️ 用纯文本把草稿（收件人 / 主题 / 正文）展示给用户，并明确询问"是否发送"，等用户回复确认' before send, '用户确认后才发送', and for batch operations '批量删除前务必让用户审核样本' plus per-batch progress reporting. A 7-item error checklist ('常见错误——你必须避免') covers the failure modes. Validation is present for every destructive/batch operation, so no cap applies. | 5 / 5 |
Progressive Disclosure | Good structure with well-labeled sections and no bundle files to navigate; the ~120-line single file is cohesive operational guidance rather than an inlined API reference, and schema details are deferred to the tools themselves. Falls short of a 5 because the trailing '操作速查' partially duplicates the opening tool table and the doc is above the under-50-line simple-skill threshold where sections alone would suffice. | 4 / 5 |
Total | 17 / 20 Passed |