dingtalk-cli

Use when the user wants to interact with DingTalk/钉钉 in any way — including but not limited to: reading, querying, searching, sending, replying to, forwarding, or recalling DingTalk/钉钉 chat messages and chat history; managing group chats and conversations; sending DING alerts; querying contacts, org structure, AI search, or coworkers; reading, searching, creating, or editing DingTalk/钉钉 docs, drive files, sheets, AI tables, wiki, mail, calendar events, meeting rooms, AI meeting minutes, attendance, OA approvals, todos, reports/logs, live sessions, AI apps, permissions, or open-platform docs.

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

100%

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 index skill: it front-loads a product→CLI routing table, gives a complete and executable auth/device-flow workflow, and pushes all further detail to the dws skill and --help rather than bloating SKILL.md. It assumes Claude's competence and wastes few tokens.

Dimension	Reasoning	Score
Conciseness	The body is a lean routing index — a compact product→CLI table, a terse auth section, and a short 'check --help' guide — with no explanation of concepts Claude already knows and no padding, matching the 'lean and efficient; every token earns its place' anchor.	3 / 3
Actionability	Provides concrete, executable commands such as 'dws auth status --format json', 'dws auth login --device', and 'dws chat --help', plus per-product CLI entry points in the table, matching the 'fully executable code/commands; copy-paste ready' anchor.	3 / 3
Workflow Clarity	The auth flow is explicitly sequenced with a validation checkpoint — verify 'authenticated' status, and if false run the device flow with numbered user-facing steps (show URL, ask user to authorize, command auto-detects) — matching the 'clear sequence with explicit validation steps' anchor; the skill itself routes rather than performing destructive ops.	3 / 3
Progressive Disclosure	SKILL.md is an organized overview that defers detail one level out — to the separate 'dws' skill via read_skills and to per-command '--help' — with no nested/bundled references and clear section organization, matching the 'clear overview with well-signaled one-level-deep references' anchor; no bundle files exist to contradict this.	3 / 3
	Total	12 / 12 Passed

Description

100%

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, explicit trigger-and-capability statement: it names the product, lists concrete actions, gives a clear 'Use when' clause, and stays narrowly scoped to DingTalk. It is long but every term earns its place and there is no vague fluff.

Dimension	Reasoning	Score
Specificity	Enumerates many concrete actions across products — 'reading, querying, searching, sending, replying to, forwarding, or recalling DingTalk chat messages and chat history' plus docs, sheets, wiki, mail, calendar, attendance, OA approvals, todos — matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	Opens with an explicit 'Use when the user wants to interact with DingTalk/钉钉 in any way' trigger and follows with a comprehensive 'what' list, clearly answering both what and when; voice is third-person ('the user wants'), so no voice penalty applies.	3 / 3
Trigger Term Quality	Broad coverage of natural user phrasing (chat messages, chat history, group chats, DING alerts, contacts, docs, drive files, sheets, wiki, mail, calendar, attendance, OA approvals, todos, reports/logs) including the Chinese 钉钉 term, matching the 'good coverage of natural terms' anchor; not merely jargon.	3 / 3
Distinctiveness Conflict Risk	Scoped tightly to DingTalk/钉钉 with product-specific triggers (DING alerts, AI tables, OA approvals, meeting minutes) that would not plausibly fire for unrelated skills, matching the 'clear niche with distinct triggers' anchor.	3 / 3
	Total	12 / 12 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: dtyq/magic
Path: backend/super-magic/agents/skills/dingtalk-cli/SKILL.md
Commit: 41d7ef4

Reviewed: about 13 hours ago

Table of Contents

Discovery Implementation Validation

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.