CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

77

Quality

96%

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

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

A clean, token-efficient index skill that routes to the right DingTalk CLI product, sets up authentication with executable commands and a clear device-flow sequence, and delegates depth to the `dws` skill via a well-signaled one-level reference. The only soft spot is that core operational workflows live in the delegated skill, not sequenced in this body.

Suggestions

Add a short validation checkpoint after a representative destructive operation (e.g., recall/send) — such as checking the command's JSON response for success — so the workflow_clarity sequence demonstrates the feedback loop even though detailed rules live in the `dws` skill.

Show one concrete end-to-end example command for a common operation (e.g., `dws chat send` or `dws calendar event list`) beyond auth and `--help`, to make the routing table's entry points immediately actionable.

DimensionReasoningScore

Conciseness

The body is lean: a dense product table, a few executable auth/help commands, and brief numbered steps, with no padding or explanation of concepts Claude already knows. The only prose (why to load the `dws` skill) earns its place.

5 / 5

Actionability

It gives copy-paste-ready commands (`dws auth status --format json`, `dws auth login --device`, `dws --help`, `dws <product> --help`) plus a product→CLI-entry routing table, covering the common entry cases of auth, routing, and help.

5 / 5

Workflow Clarity

The auth flow is a clear sequence with a checkpoint (verify `authenticated`, then device login with the "Waiting for user authorization" prompt) and a re-login branch, but the actual send/recall/approval workflows are delegated to the `dws` skill rather than sequenced here, leaving minor gaps.

4 / 5

Progressive Disclosure

It is explicitly an index ("DingTalk CLI Skill Index") that loads the `dws` skill one level deep for full details, with well-organized sections (overview table, auth, help) and clearly signaled navigation.

5 / 5

Total

19

/

20

Passed

Description

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

A strong, comprehensive description that names a wide range of concrete DingTalk capabilities, uses natural trigger terms with synonyms, and explicitly states both what the skill does and when to use it. It is third-person trigger-voiced and tightly scoped to DingTalk.

DimensionReasoningScore

Specificity

The description enumerates many concrete actions across products — "reading, querying, searching, sending, replying to, forwarding, or recalling" messages, "managing group chats", "creating, or editing DingTalk docs" — giving comprehensive coverage rather than vague abstractions.

5 / 5

Completeness

It explicitly answers both what (the enumerated DingTalk capabilities) and when ("Use when the user wants to interact with DingTalk in any way") with concrete trigger phrases.

5 / 5

Trigger Term Quality

It packs in natural terms a user would say ("chat messages", "chat history", "group chats", "DING alerts", "docs", "drive files", "sheets", "wiki", "mail", "calendar events", "todos") including synonyms and product-specific vocabulary.

5 / 5

Distinctiveness Conflict Risk

"DingTalk" is a specific named product niche with distinct triggers, so overlap with other skills is minimal.

5 / 5

Total

20

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
dtyq/magic
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.