CtrlK
BlogDocsLog inGet started
Tessl Logo

dingtalk-mail

钉钉邮箱读写、搜索、回复与转发。Use when 用户说发邮件/查邮件/回邮件/转发邮件/未读邮件/邮件搜索/邮箱附件。一句话发邮件时先用 dingtalk-contact 解析并确认收件人,再由本 skill 发送;不做钉钉消息(走 dingtalk-chat)、紧急通知(走 dingtalk-misc)。命令前缀:dws mail。

73

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

85%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, well-structured skill body with clear sequenced SOPs, an explicit validation checkpoint on the destructive send operation, and clean one-level-deep progressive disclosure to verified reference files. Its only weakness is redundant restatement of the --format json rule and safety prohibitions across each SOP.

Suggestions

State the '--format json' requirement and the '禁止编造 messageId / 禁止猜测邮箱' prohibitions once in a global constraints section, then reference them from each SOP instead of repeating the full text in SOP-1 through SOP-4.

Consolidate the per-SOP '禁止' lines into the existing '高频硬约束' checklist to remove near-duplicate phrasing while preserving the safety emphasis.

Consider trimming or collapsing the 10-row shortcuts table to the highest-value entries, since several (e.g. +unread-mail, +search-mail) overlap capabilities already covered by the SOPs and references.

DimensionReasoningScore

Conciseness

The body is command-dense and assumes Claude's competence (no concept explanations), but it could be tightened: the '--format json' requirement and the '禁止编造 messageId/猜测邮箱' prohibitions are restated across all four SOPs, which is redundant rather than lean.

2 / 3

Actionability

It provides fully executable commands with concrete flags (e.g. 'dws mail message send --from … --to … --subject … --content … --format json') and real, verified script invocations ('python scripts/mail_unread_summary.py', 'python scripts/mail_send_with_cc.py --to … --cc …'), which is copy-paste ready rather than pseudocode.

3 / 3

Workflow Clarity

SOP-1 through SOP-4 are clearly numbered sequences with explicit triggers and required steps, and the destructive send workflow (SOP-3) includes an explicit validation checkpoint ('验证(必须) … dws mail message verify') plus a '高频硬约束' checklist, so validation is not missing.

3 / 3

Progressive Disclosure

The body is a concise overview pointing to one-level-deep references — mail.md (command ref), 09-mail.md (multi-step), intent-guide.md, lite-recipes.md — all of which exist and are clearly signaled, with detailed content appropriately split out of SKILL.md.

3 / 3

Total

11

/

12

Passed

Description

100%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, dense description that names concrete actions, provides natural trigger terms, gives an explicit 'Use when' clause, and clearly delineates boundaries against adjacent skills. It uses third-person voice with no padding or concept explanation.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "读写、搜索、回复与转发" (read/write, search, reply, forward) — plus explicit routing to dingtalk-contact/dingtalk-chat/dingtalk-misc, matching the 'lists multiple specific concrete actions' anchor rather than the 'some actions, not comprehensive' level 2.

3 / 3

Completeness

It explicitly states both what ("钉钉邮箱读写、搜索、回复与转发") and when (an explicit 'Use when …' trigger clause), so it is not capped at 2 by the missing-trigger-guideline rule.

3 / 3

Trigger Term Quality

The 'Use when 用户说发邮件/查邮件/回邮件/转发邮件/未读邮件/邮件搜索/邮箱附件' clause gives seven natural phrasings a user would actually say, covering common variations rather than just a single technical term.

3 / 3

Distinctiveness Conflict Risk

Clear niche with explicit boundary statements — "不做钉钉消息(走 dingtalk-chat)、紧急通知(走 dingtalk-misc)" and "先用 dingtalk-contact 解析并确认收件人" — making it unlikely to trigger for the wrong skill.

3 / 3

Total

12

/

12

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

relative_links

Relative link issues: 1 suspicious

Warning

Total

13

/

16

Passed

Repository
DingTalk-Real-AI/dingtalk-workspace-cli
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.