CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

dingtalk-shared

钉钉(DingTalk) MultiSkill 的轻量共享入口。Use when 用户泛称 DWS/钉钉操作但未明确产品、请求跨产品编排、需要 URL 类型预检或产品边界消歧。清晰的单产品操作优先使用对应 dingtalk-* 子 skill;本 skill 只提供全局执行契约和按需 reference 导航,不承载产品命令全集。

Quality

85%

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

81%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 dense, well-structured execution contract: the situation→reference loading table, sequenced routing order, and bounded error-retry path with explicit validation gates make it highly actionable for its router role. The main gaps are minor: some duplicated error-handling rules between the inline contract and the error section, and a few orphaned bundle files not reachable from SKILL.md.

Suggestions

Consolidate the unknown command/flag fallback rules so they appear once — either in the 最小 DWS 执行契约 block or in 错误最短路径 — with the other location cross-referencing it, removing the current duplication.

Link or remove the orphaned bundle files (channel-login.md, runtime-contract.md, recipes/meta.md) from the 渐进加载 table or a bundle index so every reference is discoverable from SKILL.md.

Break the run-on contract sentences (e.g., the Schema/Help fallback bullet) into discrete rules so each fallback condition and its one-retry bound is scannable without re-parsing.

DimensionReasoningScore

Conciseness

Very lean, telegraphic rule lists with essentially no padding and no explanation of concepts Claude already knows (e.g., "只用 dws;结构化读取加 --format json,按真实返回判断"). Not 5 because the unknown command/flag handling rules appear in both the inline contract block and again in 错误最短路径, and the contract block packs multiple fallback policies into single run-on sentences.

4 / 5

Actionability

Concrete, executable guidance throughout: real commands and flags ("dws auth login --intl", "--format json", "--yes", "--verbose") and field-level specifics for the URL chain ("extension=dlink 时将 drive info 的 result.fileId 保存为入口 ID 并传给 dws doc info,再按 linkSourceInfo.nodeId 逐跳解析"). Not 5 because several steps remain at policy level or delegate mechanics to references ("按行动指南组合需要的产品 skill", "按真实返回判断") rather than fully specifying execution.

4 / 5

Workflow Clarity

The 路由顺序 section is a clearly sequenced 5-step precedence order, and the error path has explicit bounded feedback loops: "写后验证结果,不凭退出码宣称成功", confirmation gate before adding --yes, "只有明确 retryable=true 时才按服务端节奏重试", and one-retry caps for unknown flag. Terminal states are enumerated (完成、部分、阻塞、待确认、失败). This satisfies the validation requirement for write/batch operations.

5 / 5

Progressive Disclosure

The 渐进加载 table cleanly maps each situation to exactly one existing one-level-deep reference file, and all 11 referenced paths exist in the bundle. Not 5 because channel-login.md, runtime-contract.md, and recipes/meta.md sit in references/ unreferenced from SKILL.md, and the ../dingtalk-misc/references/profile.md link points outside this bundle — minor navigation gaps.

4 / 5

Total

17

/

20

Passed

Description

87%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 router/meta-skill description: it explicitly states what it provides, gives concrete 'Use when' triggers for ambiguity and cross-product cases, and explicitly defers single-product work to sibling skills. Its only weaknesses are function-level rather than command-level action descriptions and slightly technical trigger phrasing.

DimensionReasoningScore

Specificity

Lists several concrete functions — "需要 URL 类型预检或产品边界消歧", "全局执行契约和按需 reference 导航", "跨产品编排" — beyond just naming the domain. Not 5 because the actions stay at the function/navigation level ('轻量共享入口') rather than comprehensively enumerating concrete operations.

4 / 5

Completeness

Explicitly answers both: what ("轻量共享入口...只提供全局执行契约和按需 reference 导航,不承载产品命令全集") and when ("Use when 用户泛称 DWS/钉钉操作但未明确产品、请求跨产品编排、需要 URL 类型预检或产品边界消歧") with concrete trigger phrases. Anchor 4 ('when could be more explicit or specific') does not fit since the when-clause is fully explicit.

5 / 5

Trigger Term Quality

Natural trigger terms users would actually say are present: "用户泛称 DWS/钉钉操作", "请求跨产品编排". Not 5 because coverage lacks common variations/synonyms (e.g., specific product words like 文档/表格/日历), and terms like "产品边界消歧" lean technical.

4 / 5

Distinctiveness Conflict Risk

Clear niche (ambiguous/cross-product/URL-precheck entry) with an explicit carve-out — "清晰的单产品操作优先使用对应 dingtalk-* 子 skill" — that actively routes single-product requests away, minimizing conflict with sibling skills.

5 / 5

Total

18

/

20

Passed

Validation

75%

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

Validation — 12 / 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 deeper-than-1-level, 1 suspicious

Warning

referenced_paths_exist

Referenced path issues: 2 deeper-than-1-level

Warning

Total

12

/

16

Passed

Repository

DingTalk-Real-AI/dingtalk-workspace-cli

Path

skills/multi/dingtalk-shared/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.