SKILLEMALL.ai

BF dingtalk-docs-skill

当用户想要操作钉钉文档或向钉钉知识库推送本地文件时使用本 Skill。支持:将 Markdown/纯文本推送为可编辑钉钉文档、原格式上传 HTML/图片/PDF/Office 等文件、拉取云端文档到本地、覆盖/追加更新文档内容、块级精确编辑、搜索与列出知识库文档、下载文件与附件、导出文档为 PDF/Word、管理节点权限、创建/重命名/移动/复制/删除文档与文件夹、初始化钉钉文档 MCP 配置。当用户想操作飞书、语雀、Notion 等其他平台、只修改本地文件、管理钉钉 IM 消息或群组时,不要使用本 Skill。

ClawHub Agent Skills author: Sean Liu v1.0.3 MIT-0 6 files body ≈ 3 542 tokens Open the sourceclawhub.ai analyzed 3 d ago

As a process F 33/100 · Will not run — References files that are not bundled: 签名URL, references/dingtalk.config

ProcedureNotionAI and agentsInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
B
87/100
safety, quality, tests
Safety 60%
100
Quality 40%
67
Run on models
none yet
Process rating
F
33/100
Will not run
References files that are not bundled: 签名URL, references/dingtalk.config
Tools and files w 18
0
Result and completion w 14
0
Inputs and preconditions w 11
0
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
  2. The text references files that are not there: add them or drop the references.
For the model run — optional
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 0

✓ No critical or high findings

Files scanned: 4. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • warning missing-ref reference to a missing file: 签名URL
  • warning missing-ref reference to a missing file: references/dingtalk.config

Process rating: all ten parameters 33/100

Will not run. References files that are not bundled: 签名URL, references/dingtalk.config
  • 0Tools and files. 2 referenced file(s) missing: 签名URL, references/dingtalk.config
  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 39 mutating operations with no state check
  • 100Steps. 97 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 3542 tokens
  • low 13 top-level sections: this looks like several domains in one skill
  • medium 13 test cases, all positive: not one "should refuse" or "should ask first"
  • low No test case covers injection arriving through data

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +3Description length 259: enough signal without eating the budget
  • +4Structure: 29 headings
  • +3Step-by-step instructions: 97 items
  • +4Has examples (6 code blocks)
  • +4Reference files are cited in the instructions (1 of 1)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 67.

External checks

ClawHub: suspicious
The skill is coherent for DingTalk document work, but it asks agents to store a personal API-key-bearing MCP URL in persistent configuration, including workspace files that could be committed or shared.
LLM: suspicious (high) · 10 Sept 2026