BD dida365
滴答清单 (Dida365) API 集成,支持自建 OAuth 认证。管理任务和项目。 当用户想要在滴答清单中创建、更新、完成或组织任务和项目时使用此 Skill。 需要用户在 developer.dida365.com 创建应用并配置 DIDA365_CLIENT_ID、DIDA365_CLIENT_SECRET 环境变量。
As a process D 41/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- 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 · 2
✓ No critical or high findings
Medium and low: 2
-
low Exfiltration
net-credential-useSKILL.md:491Credential used in a network call (verify the destination is the intended service) (the skill's own vendor host)curl -s -H "Authorization: Bearer $TOKEN" https://api.…com/open/v1/project | python3 -m json.tool
vendor-host -
low Exfiltration
net-credential-useSKILL.md:532Credential used in a network call (verify the destination is the intended service) (the skill's own vendor host)curl -s -o /dev/null -w "%{http_code}" -H "Authorization: Bearer $TOKEN" https://api.…com/open/v1/projectvendor-host
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 41/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
- 40Consistency. Frontmatter name (dida365) differs from the folder (dida365-api)
- 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
- 100Steps. 27 steps
- 100Execution cost. Instruction body is 2652 tokens
- 100Running it twice. No mutating operations
- low 10 top-level sections: this looks like several domains in one skill
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
- -2localhost URLs: will not work for another user
- +1No license
- +2Single-language instructions
- +3Description length 165: enough signal without eating the budget
- +4Structure: 31 headings
- +3Step-by-step instructions: 27 items
- +4Has examples (27 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 70.
External checks
ClawHub: clean
This is a transparent Dida365 task-management integration guide with disclosed OAuth setup and task/project read-write access.
LLM: benign (high) · VirusTotal: · 29 May 2026