CtrlK
BlogDocsLog inGet started
Tessl Logo

dingtalk-message

钉钉消息发送技能。支持企业内部机器人(批量单聊/群聊)和 Webhook 自定义机器人两种接入方式,支持多机器人管理,支持文本、Markdown、链接、ActionCard、FeedCard等多种消息类型。

63

Quality

76%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/dingtalk-message/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is a well-structured, highly actionable CLI reference with copy-paste commands, useful DingTalk-specific constraints (Markdown subset, rate limits, error codes), and a clear first-time setup workflow with validation. It is concise and appropriately organized, with the bundled script correctly referenced.

DimensionReasoningScore

Conciseness

The body is mostly lean — executable command blocks and practical notes (rate limits, error codes, Markdown subset) that Claude does not already know — with only minor explanatory prose in the 概述 and 注意事项 sections that could be trimmed.

4 / 5

Actionability

Provides fully executable, copy-paste-ready CLI commands covering every common case (text, markdown, link, action-card, feed-card, file, group chat, robot management), each with concrete flags and arguments.

5 / 5

Workflow Clarity

The 首次配置 flow is a clear numbered sequence with an explicit verification step ('验证配置: python scripts/dingtalk.py config --show'), but the message-sending path itself has no validation checkpoint, so it falls just below a 5.

4 / 5

Progressive Disclosure

Content is organized into well-signaled sections (Webhook 消息, 企业内部机器人消息, 机器人管理) and references a single real bundle file (scripts/dingtalk.py, verified present with all documented subcommands); the inline command catalog is appropriately placed for a CLI skill, with only minor organization gaps.

4 / 5

Total

17

/

20

Passed

Description

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

The description clearly states what the skill does and enumerates concrete capabilities and message types in third person, but it omits any explicit 'when to use' trigger guidance, which caps its completeness. Adding a 'Use when...' clause would meaningfully raise the score.

Suggestions

Append an explicit trigger clause, e.g. 'Use when the user asks to send DingTalk/钉钉 messages, alerts, or notifications to individuals or groups.'

Include the English synonym 'DingTalk' alongside '钉钉' so the skill matches English-language requests too.

Lead with a concrete action verb (e.g. 'Sends 钉钉 messages...') rather than the noun phrase '钉钉消息发送技能'.

DimensionReasoningScore

Specificity

Names the domain and lists several specific capabilities — '企业内部机器人(批量单聊/群聊)', 'Webhook 自定义机器人', '多机器人管理', and concrete message types '文本、Markdown、链接、ActionCard、FeedCard' — with only minor coverage gaps (e.g. no explicit per-type send verb).

4 / 5

Completeness

The 'what' is clear ('钉钉消息发送技能...支持...消息类型') but there is no 'Use when...' clause or equivalent explicit trigger guidance, so per the rubric guideline completeness is capped at 3.

3 / 5

Trigger Term Quality

Contains natural terms a user would say like '钉钉消息发送', '单聊/群聊', and the message-type names; good coverage but missing the English synonym 'DingTalk' and common phrasings like '发钉钉消息'.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (钉钉/DingTalk messaging) with distinct triggers and specific message types, giving minimal conflict risk with other skills.

5 / 5

Total

16

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 2 missing

Warning

Total

14

/

16

Passed

Repository
agentscope-ai/ReMe
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.