CtrlK
BlogDocsLog inGet started
Tessl Logo

dingtalk-calendar

钉钉日历与会议室。Use when 用户说 约会议/查日程/订会议室/查闲忙/加参会人/改期/取消会议/今天的日程/本周日程/共同空闲。不做视频会议发起/邀请入会/会中控制(走 dingtalk-misc)、AI 听记(走 dingtalk-minutes)、待办任务(走 dingtalk-todo)。命令前缀:dws calendar。

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

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.

This is a high-quality operational skill body: fully executable commands, clearly sequenced SOPs with validation and error-recovery loops for destructive and batch operations, and disciplined deferral of a large reference behind explicit load conditions. The main improvement opportunity is trimming redundancy across the three overlapping routing tables and the duplicated 03-meeting.md gating note.

Suggestions

Merge or deduplicate the routing information spread across the 意图表 and 常用快路径 tables — several rows restate the same commands as the Shortcuts table with slightly different phrasing, which costs tokens on every load.

State the 03-meeting.md load condition once (either the top note or the '注意' section) instead of twice; the two versions differ only in wording.

Consider trimming the 20-row Shortcuts table to write/high-risk entries only, since read-only shortcuts are discoverable via 'dws shortcut list' as the file itself already notes for low-frequency capabilities.

DimensionReasoningScore

Conciseness

The body is dense and command-oriented with no concept over-explanation ('禁止把整段 JSON 原样贴出', direct CLI invocations), assuming Claude's competence. It stays at 4 rather than 5 because of real redundancy: the gating rule for 03-meeting.md is stated twice (top note and '注意'), and the Shortcuts table, 意图表, and 常用快路径 table overlap substantially in the routing they encode.

4 / 5

Actionability

Fully executable, copy-paste-ready commands with concrete flags, placeholders, and format requirements, e.g. 'dws calendar event create --title "<主题>" --start "<ISO>" --end "<ISO>" --attendees <userId1,userId2> --format json' and 'python scripts/calendar_today_agenda.py today|tomorrow|week'. It also specifies exact behavior on errors ('unknown flag' → retry once with leaf Help), matching anchor 5.

5 / 5

Workflow Clarity

SOPs are numbered with mandatory/forbidden markers and explicit validation checkpoints, including for destructive operations: SOP-2 step 3 verification ('创建返回已包含…不为"再看一遍"额外 list'), delete confirmation and post-delete narrow-window recheck ('删除终态按需回查一次'), and rollback for '+book' ('失败自动回滚删除日程'). Feedback loops exist for script failure ('立即降级到明确的 dws calendar…命令') and pagination ('返回 nextCursor 时必须继续翻页'), matching anchor 5.

5 / 5

Progressive Disclosure

The SKILL.md is a genuine overview with fast paths, and the 52KB calendar.md plus 03-meeting.md are deferred behind explicit on-demand conditions ('仅在循环日程、响应邀请…才读取对应小节'); all four referenced files and three scripts exist and are one level deep. It stays at 5 rather than 4 because navigation conditions are stated more precisely than a simple 'See X for details' — each reference has a named trigger, and the visible Shortcuts block reduces need to open references at all.

5 / 5

Total

19

/

20

Passed

Description

95%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 is a strong example: it pairs a terse domain statement with an exhaustive natural-language trigger list, explicit de-scoping of adjacent skills, and the CLI command prefix. Its only weakness is that the capability ('what') side is a bare noun phrase, forcing the reader to infer the action set from the trigger list.

DimensionReasoningScore

Specificity

The opening '钉钉日历与会议室' is a domain noun phrase without verbs, but the trigger enumeration names many concrete actions ('约会议/查日程/订会议室/查闲忙/加参会人/改期/取消会议') plus a command prefix ('dws calendar'). This matches anchor 4 (several specific actions, minor gaps) rather than 5, because the capability statement itself never states actions — they are only implicit in the 'Use when' list.

4 / 5

Completeness

Explicitly answers 'what' ('钉钉日历与会议室…命令前缀:dws calendar') and 'when' with concrete trigger phrases ('Use when 用户说 约会议/查日程/…'), plus explicit exclusions. It fits anchor 5 (both what and when with concrete trigger phrases) rather than 4, since the 'when' clause is maximally explicit — a full enumerated trigger list, not a vague condition.

5 / 5

Trigger Term Quality

Comprehensive natural phrases users would actually say, including synonyms and variations: '约会议', '查闲忙', '改期', '今天的日程', '本周日程', '共同空闲', '加参会人'. Not below 5 because no common variation of these calendar intents is obviously missing, and it also adds negative triggers for adjacent skills.

5 / 5

Distinctiveness Conflict Risk

Clear niche (calendar and meeting rooms only) with explicit negative boundaries routing overlapping intents to sibling skills ('不做视频会议…走 dingtalk-misc、AI 听记走 dingtalk-minutes、待办任务走 dingtalk-todo') and a distinct command prefix. Minimal conflict risk, matching anchor 5.

5 / 5

Total

19

/

20

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.

Validation — 13 / 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

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.