CtrlK
BlogDocsLog inGet started
Tessl Logo

dws

管理钉钉产品能力(AI表格/AI搜问/日历/通讯录/群聊与机器人/待办/审批/考勤/日志/DING消息/开放平台文档/钉钉文档/钉钉云盘/原生Markdown文件/AI听记/邮箱/在线电子表格/知识库等)。当用户需要操作表格数据、管理日程会议、模糊找人/查谁负责某事项、查询通讯录、管理群聊、机器人发消息、创建待办、提交审批、查看考勤、提交日报周报(钉钉日志模版)、读写钉钉文档、上传下载云盘文件、读取或修改原生.md文件、查询听记纪要、收发邮件、读写在线电子表格(axls)、管理钉钉知识库,或订阅个人 IM 事件、实时监听群成员加入、群成员退出、群改名和群解散时使用。

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

Failed to scan

The risk profile of this skill

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.

The body is a well-structured, highly actionable overview with clear sequencing, validation/confirmation feedback loops, and a properly organized progressive-disclosure bundle of real references and scripts. Its main weakness is conciseness: several routing/contract-drift rules are repeated across sections and could be consolidated.

Suggestions

Consolidate the repeated Schema-vs-Help precedence and shortcut-routing rules (currently restated in the Shortcut原则, 命令发现, and Schema/Help边界 sections) into one authoritative section to cut redundancy.

Trim the provenance/contract-drift mechanics (e.g. agent_metadata_source, interface_ref field listings and the repeated 'do not re-infer from Catalog/annotation' warnings) to the minimum an agent needs at runtime.

Fix the dangling reference: the 产品总览 table links to references/products/aiapp.md which does not exist in the bundle (the file is absent), so update or remove that link to avoid a broken progressive-disclosure pointer.

DimensionReasoningScore

Conciseness

The body is dense and largely efficient (tables, decision-tree triggers, command examples), but several sections restate the same Schema-vs-Help precedence and shortcut-routing rules multiple times (e.g. lines 29-36 vs 179-269 vs 249-265) and over-explain contract-drift/provenance mechanics that could be tightened, fitting the 'mostly efficient but could be tightened' anchor rather than fully lean.

2 / 3

Actionability

It gives concrete, executable commands throughout (`dws schema "calendar event create" --compact`, `dws event consume <event_key> --flatten`, `python scripts/<name>.py`) with real flag examples and a worked leaf Schema jsonc snippet, matching the 'fully executable commands; copy-paste ready' anchor.

3 / 3

Workflow Clarity

The four-step 核心流程 is explicitly sequenced, the danger-operation table pairs with a numbered 确认流程 (展示摘要→用户确认→--yes), and 错误处理 gives an ordered retry→recovery→report loop with validation checkpoints, satisfying the 'clear sequence with explicit validation steps; feedback loops' anchor.

3 / 3

Progressive Disclosure

The SKILL.md is an overview that signals one-level-deep references clearly (references/products/*, intent-guide, url-patterns, best_practices/*, scripts/) and the linked paths resolve to real files in the bundle; content is appropriately split into product/reference/script files rather than inlined, matching the 'clear overview with well-signaled one-level-deep references' 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.

This is a strong, comprehensive description that explicitly covers what the skill does and when to use it, with rich natural trigger terms and clear disambiguation against adjacent skills. Its only weakness is extreme length/verbosity, which the description rubric does not directly penalize but which strains readability.

DimensionReasoningScore

Specificity

The description enumerates many concrete capabilities across numerous DingTalk products (AI表格 record/field/view operations, 日程会议, 通讯录查询, 群聊与机器人发消息, 待办创建, 审批提交, 考勤查看, 钉钉文档读写, 云盘上传下载, .md文件读写, 听记纪要查询, 邮件收发, 电子表格axls, 知识库管理, IM事件订阅), matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

It explicitly answers both 'what' (the enumerated capability list) and 'when' via the '当用户需要...时使用' / 'Use when...' trigger clause, satisfying the explicit-trigger anchor for completeness.

3 / 3

Trigger Term Quality

It covers natural user phrasing extensively (找人/查谁负责某事项, 发邮件, 收发邮件, 提交日报周报, 读写钉钉文档, 监听群成员加入/退出), giving good coverage of terms users would actually say across the product surface.

3 / 3

Distinctiveness Conflict Risk

The DingTalk-specific scope and detailed trigger list carve a clear niche unlikely to fire for unrelated skills; the negative-scope notes (不含人才池/绩效去hrbrain) further reduce conflict with adjacent skills.

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

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 1 missing, 39 deeper-than-1-level

Warning

referenced_paths_exist

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

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.