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 exceptionally well-engineered routing skill: every user intent maps to an exact dws command with flags, defaults, and safety gates, and validation/read-back semantics plus error-recovery loops are explicit throughout. The only real deductions are near-verbatim repetition of the Help/Schema fallback policy across three sections and a second hop of reference nesting beyond the ideal one-level-deep structure.

DimensionReasoningScore

Conciseness

The body is telegraphic and assumes competence — zero concept explanations, ~115 lines routing an entire product surface. It misses 5 because the Schema/Help fallback policy ('Schema 不可用才读一次 leaf Help;unknown flag 修正一次;unknown command 禁 Help') is restated nearly verbatim in the runtime contract, the Shortcut 发现 section, and error path #2.

4 / 5

Actionability

Fully executable commands with flags, defaults, and conventions throughout: 'dws doc +create --name <标题> --content <文本|-|@文件> [--folder <ID>|--workspace <ID>]', "'-'=stdin,禁 '@-'", "'--role' 默认 READER (READER|DOWNLOADER|EDITOR|MANAGER)", covering ~20 common intents copy-paste ready, with a defined leaf-Schema fallback for unknown parameters. No anchor above fits better.

5 / 5

Workflow Clarity

Explicit sequencing ('稳定 ID → shortcut → 局部读 → 精确写'), validation checkpoints everywhere ('写后验证结果,不凭退出码宣称成功', '回读匹配才报完成', '+export 有 localPath 且 sizeBytes>0 即终态'), and feedback loops for error recovery (REVISION_CONFLICT → re-read → diff → user confirm; 'partial_success 只补未完成'; 'doc_write_commit_unknown 先回读;禁止自动重试'). Destructive/batch writes all carry verification, so the missing-validation cap does not apply.

5 / 5

Progressive Disclosure

The body is a lean routing layer with an explicit trigger→file table ('按需加载') that forbids preloading ('常规 +create、+fetch、+update... 禁止读取 reference;禁预加载/连读'), and all referenced files exist with bulk content appropriately pushed to references/doc/format/ and references/doc/style/. It is not 5 because references chain two hops (SKILL.md → doc-create.md → style/doc-create-workflow.md), and a few bundle files (doc-info.md, 04-document.md) are not reachable from the body's navigation table.

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, specific capability catalog for DingTalk online documents with good natural keyword coverage and an explicit whiteboard de-confliction pointer, but it lacks any 'when to use this skill' trigger clause, capping completeness. Adding a 'Use when...' sentence with concrete trigger scenarios (e.g., working with 钉钉文档/adoc, reading or editing online docs, exporting to docx/markdown/pdf) would raise completeness and trigger quality.

Suggestions

Add an explicit 'Use when...' clause (e.g., '当用户需要处理钉钉在线文档(adoc)、读取或编辑文档内容、导出 docx/markdown/pdf 时使用') to answer the 'when' half of completeness.

Include concrete export/import format names (docx, markdown, pdf) as trigger terms, since users asking to export a DingTalk doc will name the target format.

Briefly distinguish sibling-skill boundaries in the description (e.g., file storage/upload → dingtalk-drive) to reduce conflict risk, mirroring the whiteboard redirect already present.

DimensionReasoningScore

Specificity

The description enumerates many specific capabilities ('查找、读写、块、评论、附件、导入导出、版本、模板、权限、分享、Markdown/JSONML') plus concrete container actions ('插入、定位、删除'). It stays at 4 rather than 5 because capabilities are mostly listed as bare nouns rather than concrete verb phrases, and it is well above 3 given the breadth of coverage.

4 / 5

Completeness

The 'what' is clear and comprehensive, but there is no 'Use when...' clause or equivalent explicit trigger guidance for when to use this skill; the closing sentence ('白板图形内容创建或修改走 dingtalk-misc') is only negative boundary guidance pointing to another skill. Per the rubric, a missing 'Use when' clause caps completeness at 3.

3 / 5

Trigger Term Quality

Natural user terms are well covered ('评论', '附件', '导入导出', '分享', '权限', '版本', '模板', 'Markdown/JSONML'). It falls short of 5 because common variations users would actually say are missing — e.g., export formats (docx/PDF), 协作/协同编辑 synonyms, or file extensions.

4 / 5

Distinctiveness Conflict Risk

It occupies a clear niche (DingTalk online documents, 'adoc') and explicitly de-conflicts the whiteboard case ('白板图形内容创建或修改走 dingtalk-misc'). It is not 5 because overlaps with closely related sibling skills (dingtalk-drive file storage, dingtalk-wiki knowledge bases) are not disambiguated in the description itself.

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.