CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

dingtalk-doc

钉钉在线文档(adoc):查找、读写、块、评论、附件、导入导出、版本、模板、权限、分享、Markdown/JSONML;文档内白板卡片容器的插入、定位、删除。白板图形内容创建或修改走 dingtalk-misc。

Quality

79%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/multi/dingtalk-doc/SKILL.md
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.

An exemplary routing skill body: fully executable commands with explicit validation gates, recovery semantics, and read-back verification for every write path, all in an extremely lean telegraphic style. The only weaknesses are triple-stated Help/Schema recovery policy that could be consolidated and a couple of imperfect reference links in the otherwise well-structured on-demand bundle.

Suggestions

Consolidate the Help/Schema/unknown-command recovery policy into one canonical section (e.g. the DWS runtime contract) and reference it from the Shortcut 发现 and 错误最短路径 sections instead of restating it three times.

Fix the broken relative link in references/intent-guide.md to 04-document.md ("../../dingtalk-doc/references/04-document.md" should be "04-document.md") and consider surfacing 04-document.md from the body's 按需加载 table since it is currently unreachable from SKILL.md.

DimensionReasoningScore

Conciseness

The body is maximally dense telegraphic guidance with zero padding and no explanations of concepts Claude already knows, but the Help/Schema/unknown-command recovery policy is restated nearly verbatim across the DWS runtime contract, the Shortcut 发现 section, and 错误最短路径 item 2 — duplication that could be consolidated, matching anchor 4 rather than anchor 5's every-token-earns-its-place.

4 / 5

Actionability

The Golden Route table gives exact, copy-paste-ready commands with flags and boundaries (e.g. "dws doc +fetch --node <ID或URL>", "dws doc +update --node <ID或URL> --command <动作>", "dws doc +import --file <相对路径> [--folder <ID>|--workspace <ID>]") covering all common cases — search, read, create, update, export, import, comments, permissions, sharing, media.

5 / 5

Workflow Clarity

Explicit sequence ("稳定 ID → shortcut → 局部读 → 精确写") with strong validation checkpoints and feedback loops: "写后验证结果,不凭退出码宣称成功", "回读匹配才报完成", recovery semantics for partial_success/unknown/retryable, checkpoint/compensation for writes, and a REVISION_CONFLICT re-read-and-confirm-diff flow — matching anchor 5's explicit validation and error-recovery loops.

5 / 5

Progressive Disclosure

The 按需加载 trigger-condition table clearly signals one-level-deep references and all 11 referenced files exist, with aggressive anti-preloading rules; however, the bundle nests a second level (references/doc/*/format/ and style/), one top-level file (04-document.md) is only reachable via a broken relative link in intent-guide.md ("../../dingtalk-doc/references/04-document.md"), and the whiteboard boundary link points outside the bundle — minor organization gaps matching anchor 4.

4 / 5

Total

18

/

20

Passed

Description

66%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 dense, domain-specific capability enumeration that clearly identifies the DingTalk online-docs niche and includes strong natural trigger keywords, with an explicit whiteboard de-confliction. Its main weakness is the absence of any "Use when…" trigger clause, and several capabilities are listed as object nouns rather than concrete actions.

Suggestions

Add an explicit trigger clause, e.g. "当用户提到钉钉文档、adoc 链接、在线文档的读写/评论/导出/权限时使用", to raise completeness above the cap of 3.

State boundary de-conflicts with the closest sibling skills in the description (普通文件下载→drive、知识库→wiki、原生 .md→misc), as is already done for whiteboard graphics.

Convert object-noun entries into concrete actions (e.g. "块"→"创建/编辑/删除文档块", "版本"→"保存/回滚版本") and add common synonyms such as "云文档/协作文档".

DimensionReasoningScore

Specificity

Lists many concrete capability areas — "查找、读写、块、评论、附件、导入导出、版本、模板、权限、分享、Markdown/JSONML" plus "插入、定位、删除" for whiteboard card containers — but several entries ("块、评论、附件、版本") are bare object nouns rather than concrete action phrases, matching anchor 4 (several specific actions, minor gaps) rather than anchor 5's fully comprehensive concrete actions.

4 / 5

Completeness

The "what" is clear and comprehensive (full capability enumeration), but there is no "Use when…" clause or equivalent explicit trigger guidance; the trailing "白板图形内容创建或修改走 dingtalk-misc" only provides an exclusion boundary, so 'when' is at best weakly implied — capped at 3 per the judging guideline.

3 / 5

Trigger Term Quality

Good natural-keyword coverage users would actually say: "钉钉在线文档", "adoc", "评论", "导出", "模板", "权限", "分享", "附件", "白板". Not anchor 5 because common synonyms and variations (e.g. "云文档", "协作文档", "文档链接") are missing.

4 / 5

Distinctiveness Conflict Risk

Names a distinct niche ("钉钉在线文档(adoc)") and explicitly de-conflicts whiteboard graphics ("白板图形内容创建或修改走 dingtalk-misc"), but terms like "导入导出", "附件", "分享" carry minor overlap risk with closely related sibling skills (drive, chat, wiki) whose boundaries are not stated in the description.

4 / 5

Total

15

/

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: 8 deeper-than-1-level, 1 suspicious

Warning

referenced_paths_exist

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

Warning

Total

12

/

16

Passed

Repository

DingTalk-Real-AI/dingtalk-workspace-cli

Path

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