CtrlK
BlogDocsLog inGet started
Tessl Logo

dingtalk-chat

钉钉群聊与消息。Use when 用户提到 发消息/编辑或撤回消息/单聊/群聊/建群/普通群升级外部群/群昵称/会话分组/群成员管理/@消息/搜索聊天记录/话题回复/收藏消息/机器人群发/Webhook通知/发送或下载消息图片与文件。不做紧急 DING/短信/电话(走 dingtalk-misc)、邮件(走 dingtalk-mail)、班级群(走 dingtalk-misc)。命令前缀:dws chat。

70

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

77%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-sequenced skill body with strong SOPs and validation checkpoints, held back from a clean top score by overlapping routing layers that hurt conciseness and two dead bundle references that hurt navigation.

Suggestions

Consolidate the three overlapping routing layers (IM Shortcut 优先路由, 意图表, and SOPs) so each command's guidance lives in one place, cross-referenced rather than repeated, to remove the +messages-send / group-command redundancy.

Fix or remove the broken references: scripts/extract_media_id.py is absent from scripts/, and references/ding.md should point to the cross-skill path ../dingtalk-misc/references/ding.md (as chat.md already does).

If the three layers must stay, add a one-line header explaining when to use each (routing decisions vs. quick lookup vs. strict procedure) so the reader can skip the redundant sections.

DimensionReasoningScore

Conciseness

The body is dense, operational, and avoids explaining concepts Claude already knows, but it carries real redundancy: the same +messages-send / group commands appear across three overlapping layers (IM Shortcut 优先路由, 意图表, and the SOPs), so not every token earns its place. It is mostly efficient but could be tightened rather than fully lean.

2 / 3

Actionability

Concrete, executable commands with real flags and placeholders throughout (e.g. 'dws chat +messages-send --as user --open-dingtalk-id <id> --text "<内容>"' and 'dws aisearch person --keyword "<姓名>" --dimension name --format json'), copy-paste ready and specific rather than abstract.

3 / 3

Workflow Clarity

Each SOP is clearly sequenced (解析→执行→验证) with explicit validation steps, prohibitions, and feedback loops; destructive/batch ops carry confirmation (踢人不可逆先确认, 全部已读必须先与用户确认) and recall requires re-querying for a real openMessageId, so the destructive-ops cap does not apply.

3 / 3

Progressive Disclosure

Structure is otherwise strong — clear overview, one-level-deep signaled references, appropriate split of the 33KB chat.md command reference, and explicit runtime-deferred shortcut catalog — but two referenced paths do not resolve in the bundle ('scripts/extract_media_id.py' and 'references/ding.md'), undermining easy navigation enough to fall below the clean-overview anchor.

2 / 3

Total

10

/

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 description: specific actions, natural trigger terms, explicit Use-when guidance, and explicit deconfliction routing to sibling skills. It uses the third-person 'Use when' form with no first/second-person voice to penalize.

DimensionReasoningScore

Specificity

Lists many specific concrete actions (发消息/编辑或撤回消息/单聊/群聊/建群/普通群升级外部群/群昵称/会话分组/群成员管理/@消息/搜索聊天记录/话题回复/收藏消息/机器人群发/Webhook通知/发送或下载消息图片与文件), matching the anchor for multiple specific concrete actions rather than a vague domain label.

3 / 3

Completeness

Explicitly answers both what (钉钉群聊与消息 plus the action list) and when via a clear 'Use when 用户提到…' clause, the canonical both-what-and-when pattern; it is not the level below where 'when' is only implied.

3 / 3

Trigger Term Quality

Natural terms a user would actually say (发消息、撤回消息、单聊、群聊、建群、@消息、收藏消息、机器人群发) are well covered, matching the good-coverage anchor rather than the jargon-only or partial-coverage anchors.

3 / 3

Distinctiveness Conflict Risk

Carves a clear niche and routes overlapping cases away (不做紧急 DING/短信/电话→dingtalk-misc、邮件→dingtalk-mail、班级群→dingtalk-misc), giving distinct triggers unlikely to fire the wrong skill.

3 / 3

Total

12

/

12

Passed

Validation

75%

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

Validation12 / 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

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

12

/

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.