CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

dingtalk-wiki

钉钉知识库与空间管理。Use when 用户明确说 知识库/wiki/创建、查找或列出知识库/命名的团队知识空间/个人知识库/知识库成员/库内节点创建、列表、搜索、复制、移动、删除或知识库动态。仅说“文档空间/我的文档”不触发:普通存储管理与全局文件搜索走 dingtalk-drive;节点正文读写走 dingtalk-doc。命令前缀:dws wiki。

Quality

91%

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

88%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, highly operational routing document: every command is concrete and executable, workflows are sequenced with pervasive validation gates and explicit error-recovery paths, and on-demand references are clearly organized. The weaknesses are minor: some rule text is duplicated between the contract and Shortcuts sections, and one reference points outside the skill bundle.

Suggestions

De-duplicate the Schema/Help fallback rules between the 最小 DWS 执行契约 block and the Shortcuts section — state the rule once and reference it from the other location.

Resolve the cross-skill link in references/lite-recipes.md (../../dingtalk-doc/references/doc/doc-import.md) — either verify the target exists in the deployed environment or inline the needed import steps.

Consider moving detail-level result semantics (e.g. the 成员/分页 field-by-field rules) into the existing references to slim the top-level SKILL.md.

DimensionReasoningScore

Conciseness

The body is telegraphic and assumes Claude's competence — no concept explanations, no padding; nearly every line is an operational constraint. Not 5 because the Schema/Help fallback rules are stated nearly verbatim twice (the 最小 DWS 执行契约 block and the Shortcuts section both repeat 'Schema 不可用才读一次已知 leaf Help;unknown flag 用同 leaf Help 修正一次…禁全 Catalog'), and 当前最短路径 partially re-derives Golden Route rows; these duplications could be trimmed.

4 / 5

Actionability

Commands are copy-paste ready with concrete flags, placeholders, and expected result fields: 'dws wiki +space-list --type <orgWikiSpace|myWikiSpace> --limit 50 --page-all', 'dws wiki permission set-share-scope --workspace <ID> --visibility <PRIVATE|ORGANIZATION|PUBLIC>', and the schema introspection command with a full --jq expression. Parameter bounds (成员 --limit 默认 30 范围 1-50, --users 1-30) and validation fields (autoPageComplete, spaceTypeVerified, requestedType) make the guidance fully executable across the common cases.

5 / 5

Workflow Clarity

Multi-step flows are explicitly sequenced with ordering bans ('+space-create → doc +import --workspace → +move-to-drive', 任何一步都不得在个人域提前创建), validation checkpoints gate every write (spaceTypeVerified=true 才可断言类型, 写后验证结果不凭退出码宣称成功, autoPageComplete=true 才可用列表缺席证明不存在), destructive operations require confirmation and ownership checks, and the 错误最短路径 section provides an explicit error-recovery feedback loop. This matches the 5 anchor's validate-fix-retry structure.

5 / 5

Progressive Disclosure

The 按需加载 section is a well-signaled trigger-condition table mapping to five references that all exist and are one level deep, with an explicit policy ('Golden Route 参数足够时不读 reference;否则最多读取一个'). Not 5 because dense semantic rule sections (关键结果语义, 当前最短路径) are fully inlined where a stricter split would move detail to references, and references/lite-recipes.md links cross-skill to ../../dingtalk-doc/references/doc/doc-import.md, a path outside this skill's bundle.

4 / 5

Total

18

/

20

Passed

Description

92%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 description: it names the domain, enumerates concrete triggering operations, explicitly scopes when to fire and when not to fire against sibling skills, and states the command prefix. The only gap is a few missing natural trigger terms (share/permission-related phrases) for capabilities the skill body actually supports.

Suggestions

Add share/visibility trigger phrases (e.g. 分享、权限、分享范围、公开/私有知识库) since the skill handles `permission set-share-scope` but no corresponding user phrasing appears in the description.

Consider mentioning Drive storage-space discovery (钉盘存储空间) as a supported secondary use so users asking for that can find this skill.

DimensionReasoningScore

Specificity

The description names the domain ("钉钉知识库与空间管理") and enumerates a comprehensive set of concrete operations: "创建、查找或列出知识库", "知识库成员", "库内节点创建、列表、搜索、复制、移动、删除", and "知识库动态". Multiple specific concrete actions with full coverage of the skill's operation set, matching the 5 anchor; the only action family from the body absent here is share-scope setting, which is covered under trigger_term_quality rather than specificity.

5 / 5

Completeness

Explicitly answers both: what ("钉钉知识库与空间管理", "命令前缀:dws wiki") and when ("Use when 用户明确说 知识库/wiki/…" with a concrete enumerated trigger list plus explicit exclusion rules "仅说'文档空间/我的文档'不触发"). The when-clause is fully explicit with concrete trigger phrases, matching the 5 anchor rather than the 4 anchor where the when 'could be more explicit'.

5 / 5

Trigger Term Quality

Good natural keyword coverage including the synonym pair "知识库/wiki" plus "团队知识空间/个人知识库/知识库成员/知识库动态" — phrases a DingTalk user would naturally say. Not 5 because the body supports share-scope setting (permission set-share-scope) and Drive storage-space discovery, but no trigger terms like 分享/权限/分享范围 appear; not 3 because core terms and their common synonym are present.

4 / 5

Distinctiveness Conflict Risk

Clear niche (DingTalk wiki/知识库) with explicit disambiguation against sibling skills: "普通存储管理与全局文件搜索走 dingtalk-drive;节点正文读写走 dingtalk-doc", plus a stated command prefix. Minimal conflict risk — the exclusion rules actively prevent wrong-skill triggering, matching the 5 anchor.

5 / 5

Total

19

/

20

Passed

Validation

87%

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

Validation — 14 / 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

Total

14

/

16

Passed

Repository

DingTalk-Real-AI/dingtalk-workspace-cli

Path

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