CtrlK
BlogDocsLog inGet started
Tessl Logo

dingtalk-contact

钉钉通讯录精确查询。Use when 已有 userId 后查详情、部门、职位或邮箱,按完整手机号反查用户,或查询自己、部门成员及角色。姓名模糊搜索、工号、职责、上下级走 dingtalk-aisearch,拿到 userId 后用本 skill 补详情。命令前缀:dws contact。

78

Quality

100%

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

100%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 lean, highly actionable operational guide: dense command tables, sequenced SOPs with explicit guardrails and disambiguation checkpoints, and clean progressive disclosure into verified one-level-deep references. It avoids concept re-explanation and rewards token efficiency.

DimensionReasoningScore

Conciseness

The body is dense and operational with no padding or explanation of concepts Claude already knows; every line is a command, table row, or rule that earns its place, assuming Claude's competence.

3 / 3

Actionability

Provides fully executable, copy-paste-ready commands with explicit flags throughout (e.g. 'dws contact user get --ids <userId1>,<userId2>,... --format json') and a referenced script, rather than abstract direction.

3 / 3

Workflow Clarity

SOP-1 through SOP-4 give clear numbered sequences with must-do markers, explicit '禁止' guardrails, multi-candidate disambiguation checkpoints, and the deptId=-1→1 sentinel normalization feedback loop.

3 / 3

Progressive Disclosure

SKILL.md is a concise overview linking one-level-deep bundle files (contact.md, 08-directory.md, intent-guide.md, lite-recipes.md) that all resolve to real files, with scripts kept separate; the cross-skill dws-shared ref is not part of this skill's bundle depth.

3 / 3

Total

12

/

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.

The description is specific, complete, and distinctive: it names concrete actions, provides an explicit 'Use when' trigger, and clearly delineates scope against the sibling aisearch skill. Voice is third-person imperative, so no specificity penalty applies.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — '查详情、部门、职位或邮箱', '按完整手机号反查用户', '查询自己、部门成员及角色' — plus the concrete command prefix 'dws contact', rather than vague language.

3 / 3

Completeness

Explicitly answers both what (钉钉通讯录精确查询 with scoped capabilities) and when ('Use when 已有 userId 后查详情...'), satisfying the explicit 'Use when' trigger requirement.

3 / 3

Trigger Term Quality

Covers natural user phrasing across scenarios (详情/部门/职位/邮箱/手机号反查/角色) that a user would actually say when needing contact lookups, matching the 'good coverage of natural terms' anchor.

3 / 3

Distinctiveness Conflict Risk

Explicitly partitions scope from dingtalk-aisearch ('姓名模糊搜索、工号、职责、上下级走 dingtalk-aisearch') and defines a distinct niche (精确反查 + 补详情), making wrong-skill triggering unlikely.

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

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.