CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

dingtalk-tag

钉钉数字员工的自然语言创建、查询、修改、发布、删除、能力资源、执行状态、本地 Profile 落盘与 DSH 接入。Use when 用户说创建或管理数字员工、改人设/岗位/响应模式、发布或询问下线能力、查执行状态或 trace、管理数字员工 Skill/MCP、把已有数字员工转换为本地 Profile,或接入本地 DSH。命令前缀:dws dingtalk-tag。

Quality

89%

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

78%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 strong, dense instruction body: it routes every user intent to a concrete command, states exact flags and validation rules, includes dry-run/confirm checkpoints and failure-recovery guidance for destructive operations, and discloses progressively into five real, purpose-labeled reference files. Its weaknesses are repetition between the intro, routing table, and constraint bullets, overloaded multi-clause sentences, and the absence of one complete example command for the most common create flow.

Suggestions

Deduplicate guidance that appears in multiple places — the mention_only default (intro paragraph plus two constraint bullets) and the unbind/connect flows (routing table plus four constraint bullets) — keeping policy in one authoritative location.

Add one complete, copy-paste-ready example of the most common operation, e.g. `dws dingtalk-tag manage create --name ... --description ... --type qwenwork --dry-run --format json`, so the required-argument contract is visible without opening references.

Break the longest multi-clause constraint bullets (e.g. the --type / --snapshot bullet and the 换绑 bullet) into single-rule lines or a short numbered sequence for the create → publish → connect path, making the order and checkpoints easier to follow.

DimensionReasoningScore

Conciseness

The body is information-dense with no explanation of concepts Claude already knows — every bullet carries product-specific rules (e.g. "`digitalTagEmployeeProfile.type` ... 仅支持 `qwenwork`、`local_agent`"). However, there is noticeable repetition: the `mention_only` default appears in two bullets and the intro paragraph, and unbind/connect flows appear in both the routing table and the constraint bullets, so it sits at anchor 4 ('minor instances that could be trimmed') rather than 5.

4 / 5

Actionability

Commands are concrete with exact flags and values (`--dry-run --format json`, `--agent-uuid ... --channel dsh`, `--daemon --alwayson`, `configString.mcpServers.<名称>.type`), which is mostly executable guidance. It falls short of anchor 5 because commands use `...` elision and the most common operation (create with its required name/description/type arguments) never appears as a complete example — full syntax is delegated to references, leaving minor gaps.

4 / 5

Workflow Clarity

Multi-step flows have explicit checkpoints and feedback loops: "先用 `--dry-run --format json` 展示计划" then "确认后才加 `--yes`", "旧机器 `connect unbind` 成功后,新机器 ... connect", and failure recovery like "connect 失败后 ... 检查 `connect status` 再恢复" and "重试禁止再次执行 create". Destructive operations do have validation, so no cap applies, but sequences are scattered across bullets rather than consolidated, leaving minor gaps versus anchor 5's explicit checklists.

4 / 5

Progressive Disclosure

The body is a concise overview that clearly signals one-level-deep references, all of which exist in the bundle: "先用 [dingtalk-tag-index.md] 路由;生命周期读取 [manage.md] ... 能力资源读取 [capability.md];执行排障读取 [run.md]" (plus manage-and-connect.md). Content is appropriately split (a ~45-line body routing to five purpose-labeled reference files), matching anchor 5's clear overview with well-signaled references; it is not anchor 4 because navigation is complete and unambiguous.

5 / 5

Total

17

/

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.

The description is exemplary: it enumerates the skill's concrete capabilities, gives an explicit and thorough 'Use when' trigger list with natural user phrasings and synonyms, states the command prefix, and occupies a distinct niche with minimal conflict risk. It uses neutral third-person phrasing with no first/second-person voice and no vague padding.

DimensionReasoningScore

Specificity

The description enumerates concrete lifecycle actions — "自然语言创建、查询、修改、发布、删除、能力资源、执行状态、本地 Profile 落盘与 DSH 接入" — covering the skill's full scope rather than vague domain language. It lists multiple specific actions with comprehensive coverage, matching the anchor-5 example's structure; nothing here is generic filler, so 4's 'minor gaps' does not apply.

5 / 5

Completeness

It explicitly answers both questions: 'what' via the action enumeration and 'when' via a concrete "Use when 用户说..." trigger list, plus the command prefix "命令前缀:dws dingtalk-tag". This mirrors the anchor-5 example (explicit what + when with concrete trigger phrases); it is clearly above anchor 4, where 'when' is only loosely specified.

5 / 5

Trigger Term Quality

The 'Use when' clause includes natural phrases users would actually say: "创建或管理数字员工、改人设/岗位/响应模式、发布或询问下线能力、查执行状态或 trace、管理数字员工 Skill/MCP、把已有数字员工转换为本地 Profile,或接入本地 DSH", with synonym variations (人设/岗位/响应模式). Coverage is comprehensive for this CLI domain (no file extensions apply), so it exceeds anchor 4's 'a few natural terms missing'.

5 / 5

Distinctiveness Conflict Risk

The niche is sharply defined — DingTalk 数字员工 management via the `dws dingtalk-tag` command prefix — with triggers specific to digital-employee lifecycle and DSH/Profile operations, so overlap with sibling dingtalk skills is minimal. It matches anchor 5's 'clear niche with distinct triggers' rather than anchor 4's 'minor overlap risk with closely related skills'.

5 / 5

Total

20

/

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: 2 suspicious

Warning

Total

13

/

16

Passed

Repository

DingTalk-Real-AI/dingtalk-workspace-cli

Path

skills/multi/dingtalk-tag/SKILL.md

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.