CtrlK
BlogDocsLog inGet started
Tessl Logo

dingtalk-ding

DING 紧急消息(应用内 / 短信 / 电话)。Use when 用户说 DING一下/紧急通知/电话DING/短信DING/必达消息/电话叫人。Distinct from dingtalk-chat(普通群聊消息)、dingtalk-outbound-call(企业外呼)。命令前缀:dws ding。

74

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

87%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.

The body is concise and actionable with good progressive disclosure via one real reference file. The main gap is workflow clarity: high-risk recall and cost-bearing sms/call operations lack explicit confirmation/validation checkpoints in the body itself.

Suggestions

Add an explicit confirm-before-send checkpoint for cost-bearing channels (sms/call) and a verify-before-recall step for +recall-personal in the body, since these are high-risk-write operations.

Surface the "sms/call 有通信费用,使用前需和用户确认" safety note from references/ding.md directly in the body near the intent table so the validation step is not only in the reference.

Include a brief validate-then-proceed loop (e.g. dry-run or --format json output check) for recall/send workflows to lift workflow_clarity above 2.

DimensionReasoningScore

Conciseness

The body is lean — shortcut table, intent table, and cross-product notes — with no concept explanations Claude already knows; structural preamble markers and routing policy are operational, not padding. Closest to the lean/efficient anchor.

3 / 3

Actionability

The intent table maps user phrases to copy-paste-ready commands (e.g. `dws ding message send --type app --users <userId> --content "<内容>"`) and lists shortcuts with risk levels, giving fully executable guidance.

3 / 3

Workflow Clarity

Routing and sequencing are present, but the body includes high-risk-write (+recall-personal) and cost-bearing (sms/call) operations without explicit validation/confirmation checkpoints, which the rubric caps at 2 for destructive or batch operations.

2 / 3

Progressive Disclosure

A concise overview with a single, clearly signaled one-level-deep reference ("命令参考:[ding.md](references/ding.md)"), and references/ding.md exists with no nested references, matching the clear-overview anchor.

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 tight, well-targeted description: concrete capability surfaces, natural trigger phrasings, an explicit Use-when clause, and explicit disambiguation from sibling skills. Voice is appropriately third-person/declarative with no fluff.

DimensionReasoningScore

Specificity

Names concrete capability surfaces — "应用内 / 短信 / 电话" — listing multiple specific DING delivery channels rather than vague language, matching the score-3 anchor that enumerates specific actions.

3 / 3

Completeness

Answers both what ("DING 紧急消息(应用内 / 短信 / 电话)") and when (explicit "Use when" clause with concrete triggers), satisfying the both-what-and-when anchor.

3 / 3

Trigger Term Quality

"Use when 用户说 DING一下/紧急通知/电话DING/短信DING/必达消息/电话叫人" covers natural phrasings a user would actually say, matching the good-coverage anchor.

3 / 3

Distinctiveness Conflict Risk

"Distinct from dingtalk-chat(普通群聊消息)、dingtalk-outbound-call(企业外呼)" plus a "命令前缀:dws ding" carve a clear niche unlikely to trigger 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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

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.