CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

dingtalk-chat

钉钉群聊与消息。Use when 收发/搜索消息、建群、群治理、Bot/Webhook、文件、AI/A2UI 卡片流式,或仅限 IM 的消息谓词筛选。跨源主题/行为轨迹走 dingtalk-aisearch;DING/班级群走 dingtalk-misc;邮件走 dingtalk-mail。

Quality

91%

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

92%Weight 40%Scale 1-5

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

A dense, highly operational CLI-routing skill: executable commands with flags for every common case, explicit write lifecycle with validation and retry semantics, and a clean one-level-deep reference structure fully backed by the actual bundle. The sole trim opportunity is the near-duplicated Schema/Help contract text repeated across the runtime-contract and shortcut sections.

DimensionReasoningScore

Conciseness

The body is exceptionally lean telegraphic guidance with zero explanation of known concepts (e.g. "只用 dws;结构化读取加 --format json,按真实返回判断", "禁 head 截 JSON"). Not a 5 because the Schema/Help/unknown-command rules are stated near-verbatim twice — once in "最小 DWS 执行契约" and again in "Shortcut 发现" — so a small block of tokens does not earn its place twice.

4 / 5

Actionability

The Golden Route table gives copy-paste-ready commands with concrete flags for the common cases ("dws chat +dm --to <姓名> --content <内容>", "dws chat message list-all --start <开始> --end <结束> --page-all --no-reactions") plus a fully specified schema-inspection command with an inline --jq expression. Anchor 5: executable, complete, covering the common cases.

5 / 5

Workflow Clarity

Multi-step writes have an explicit validate-then-execute-then-verify sequence ("多步骤写先校验目标、限制、内容、确认,再沿稳定 ID 串行执行并验证"), post-write validation ("写后验证结果,不凭退出码宣称成功", "写后读回"), and a numbered error-recovery feedback loop ("仅 retryable=true 按原命令重试一次… confirmation_required 等用户确认,不补 --yes"). Anchor 5; the destructive/batch validation cap does not apply because validation is present.

5 / 5

Progressive Disclosure

SKILL.md is a routing overview with a scenario→reference "按需加载" table, and all 14 in-bundle referenced paths (references/chat/message-query.md, references/chat/group-admin.md, references/card/a2ui.md, etc.) verified to exist exactly one level deep. The only out-of-bundle pointer is the cross-skill handoff "../dingtalk-event/SKILL.md", which is a sibling-skill reference, not nested detail.

5 / 5

Total

19

/

20

Passed

Description

92%Weight 40%Scale 1-5

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: concise, third-person, with an explicit 'Use when' trigger clause listing concrete capabilities and explicit boundary routing to three sibling skills. The only gap is a handful of natural synonyms (私聊/单聊, 未读, @消息) that users might phrase differently from the listed triggers.

DimensionReasoningScore

Specificity

The 'what' ("钉钉群聊与消息") is followed by multiple concrete capability areas: "收发/搜索消息、建群、群治理、Bot/Webhook、文件、AI/A2UI 卡片流式" and "消息谓词筛选" — comprehensive, action-level coverage of the IM domain. Not a 4 because coverage is essentially exhaustive for the niche with no generic filler actions.

5 / 5

Completeness

Both parts are explicit: 'what' via "钉钉群聊与消息" plus the capability list, and 'when' via the "Use when 收发/搜索消息、建群、群治理、Bot/Webhook、文件、AI/A2UI 卡片流式,或仅限 IM 的消息谓词筛选" clause with concrete trigger phrases. Anchor 5 fits; it is not a 4 because the 'when' is already specific, not merely present.

5 / 5

Trigger Term Quality

Natural user terms are present ("群聊", "消息", "收发/搜索", "建群", "Bot/Webhook", "文件", "邮件", "DING", "班级群"), but common variations a user would say are missing — e.g. "私聊/单聊" (DM), "未读", "@我的消息", "转发/撤回". Matches anchor 4 (good coverage, a few natural terms missing) rather than 5's synonym-level completeness.

4 / 5

Distinctiveness Conflict Risk

A clear niche (DingTalk IM only, "仅限 IM 的消息谓词筛选") with explicit negative routing to sibling skills: "跨源主题/行为轨迹走 dingtalk-aisearch;DING/班级群走 dingtalk-misc;邮件走 dingtalk-mail". This actively minimizes wrong-skill triggering; anchor 5, not 4, because overlap risks are disambiguated rather than merely minor.

5 / 5

Total

19

/

20

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.

Validation — 12 / 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: 13 deeper-than-1-level, 1 suspicious

Warning

referenced_paths_exist

Referenced path issues: 13 deeper-than-1-level

Warning

Total

12

/

16

Passed

Repository

DingTalk-Real-AI/dingtalk-workspace-cli

Path

skills/multi/dingtalk-chat/SKILL.md

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.