SKILLEMALL.ai

BD dingtalk-todo

钉钉待办管理。当用户提到"钉钉待办"、"待办任务"、"创建待办"、"新增待办"、"查看待办"、"完成待办"、"标记完成"、"删除待办"、"待办列表"、"我的待办"、"设置截止时间"、"指派待办"、"dingtalk todo"、"todo task"、"task management"时使用此技能。支持:创建待办(含描述/截止时间/优先级/参与者)、获取详情、查询列表(按完成状态过滤)、更新待办、标记完成、删除待办等全部待办类操作。

ClawHub Agent Skills author: breath57 v0.1.0 MIT-0 3 files body ≈ 1 180 tokens Open the sourceclawhub.ai analyzed 3 d ago

As a process D 46/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions

ReferencePersonal productivitytype and topics are labelled automatically from the skill text
JSON
Technical rating
B
86/100
safety, quality, tests
Safety 60%
92
Quality 40%
76
Run on models
none yet
Process rating
D
46/100
Unfinished process
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
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.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 8

✓ No critical or high findings

Medium and low: 8
  • low Exfiltration exfil-secret-in-url SKILL.md:50
    Credential passed in a URL query string (normal for some APIs — verify the host is the intended service) (placeholder value)
    OLD_TOKEN=$(curl -s "https://oapi.dingtalk.com/gettoken?appkey=…&appsecret=…" | grep -o '"access_token":"[^"]*"' | cut -d'"' -f4)
    placeholder
  • low Exfiltration net-credential-use SKILL.md:50
    Credential used in a network call (verify the destination is the intended service) (the skill's own vendor host)
    OLD_TOKEN=$(curl -s "https://oapi.dingtalk.com/gettoken?appkey=…&appsecret=…" | grep -o '"access_token":"[^"]*"' | cut -d'"' -f4)
    vendor-host
  • low Exfiltration exfil-secret-in-url SKILL.md:53
    Credential passed in a URL query string (normal for some APIs — verify the host is the intended service) (placeholder value)
    UNION_ID=$(curl -s -X POST "https://oapi.dingtalk.com/topapi/v2/user/get?access_token=…" \
    placeholder
  • low Exfiltration net-credential-use SKILL.md:53
    Credential used in a network call (verify the destination is the intended service) (the skill's own vendor host)
    UNION_ID=$(curl -s -X POST "https://oapi.dingtalk.com/topapi/v2/user/get?access_token=…" \
    vendor-host
  • low Exfiltration exfil-secret-in-url SKILL.md:96
    Credential passed in a URL query string (normal for some APIs — verify the host is the intended service) (placeholder value)
    OLD_TOKEN=$(curl -s "https://oapi.dingtalk.com/gettoken?appkey=…&appsecret=…" | grep -o '"access_token":"[^"]*"' | cut -d'"' -f4)
    placeholder
  • low Exfiltration net-credential-use SKILL.md:96
    Credential used in a network call (verify the destination is the intended service) (the skill's own vendor host)
    OLD_TOKEN=$(curl -s "https://oapi.dingtalk.com/gettoken?appkey=…&appsecret=…" | grep -o '"access_token":"[^"]*"' | cut -d'"' -f4)
    vendor-host
  • low Exfiltration exfil-secret-in-url SKILL.md:97
    Credential passed in a URL query string (normal for some APIs — verify the host is the intended service) (placeholder value)
    UNION_ID=$(curl -s -X POST "https://oapi.dingtalk.com/topapi/v2/user/get?access_token=…" \
    placeholder
  • low Exfiltration net-credential-use SKILL.md:97
    Credential used in a network call (verify the destination is the intended service) (the skill's own vendor host)
    UNION_ID=$(curl -s -X POST "https://oapi.dingtalk.com/topapi/v2/user/get?access_token=…" \
    vendor-host

Files scanned: 3. 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")

Process rating: all ten parameters 46/100

  • 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
  • 60Tools and files. Uses tools (bash) that frontmatter does not declare
  • 100Steps. 8 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1180 tokens
  • 100Running it twice. No mutating operations

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

  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • -5TODO / placeholder text left in the skill
  • +1No license
  • +2Single-language instructions
  • +5Description quotes 4 example trigger phrases
  • +3Description length 218: enough signal without eating the budget
  • +4Structure: 8 headings
  • +3Step-by-step instructions: 8 items
  • +4Has examples (3 code blocks)
  • +4Reference files are cited in the instructions (1 of 1)

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

External checks

ClawHub: suspicious
This DingTalk todo skill is mostly coherent, but it asks for persistent DingTalk credentials and can modify real business tasks while using broad triggers that could invoke it unexpectedly.
LLM: suspicious (high) · VirusTotal: · 29 May 2026