BD yida-dev
钉钉宜搭低代码开发助手。用于创建表单和自定义页面、编写 JS 动作面板、使用 JS-API、配置数据源、设计流程自动化。适用于宜搭表单开发、JS 代码调试、API 集成等场景。
钉钉宜搭低代码开发助手。用于创建表单和自定义页面、编写 JS 动作面板、使用 JS-API、配置数据源、设计流程自动化。适用于宜搭表单开发、JS 代码调试、API 集成等场景。
As a process D 49/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
IntegrationSoftware developmentPersonal productivitytype and topics are labelled automatically from the skill text
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 · 9
✓ No critical or high findings
Medium and low: 9
-
low Exfiltration
net-credential-usescripts/integration_example.js:49Credential used in a network call (verify the destination is the intended service) (test fixture / example file)const response = await fetch(`${this.config.baseUrl}${endpoint}?access_token=${accessToken}`, {fixture -
low Exfiltration
net-credential-usescripts/server_api_example.js:57Credential used in a network call (verify the destination is the intended service) (test fixture / example file)const response = await fetch(`${this.baseUrl}/yida/process/start?access_token=${token}`, {fixture -
low Exfiltration
net-credential-usescripts/server_api_example.js:83Credential used in a network call (verify the destination is the intended service) (test fixture / example file)const response = await fetch(`${this.baseUrl}/yida/process/instance/delete?access_token=${token}`, {fixture -
low Exfiltration
net-credential-usescripts/server_api_example.js:106Credential used in a network call (verify the destination is the intended service) (test fixture / example file)const response = await fetch(`${this.baseUrl}/yida/process/instance/terminate?access_token=${token}`, {fixture -
low Exfiltration
net-credential-usescripts/server_api_example.js:130Credential used in a network call (verify the destination is the intended service) (test fixture / example file)const response = await fetch(`${this.baseUrl}/yida/form/instance/query?access_token=${token}`, {fixture -
low Exfiltration
net-credential-usescripts/server_api_example.js:154Credential used in a network call (verify the destination is the intended service) (test fixture / example file)const response = await fetch(`${this.baseUrl}/yida/form/data/save?access_token=${token}`, {fixture -
low Secrets in code
secret-high-entropy-tokenSKILL.md:39High-entropy token-like string (may be an id, hash or a credential) (documentation table row)| 部门选择 | `depa…4i5` |
table -
low Secrets in code
secret-high-entropy-tokenSKILL.md:42High-entropy token-like string (may be an id, hash or a credential) (documentation table row)| 关联表单 | `asso…50s` |
table -
low Secrets in code
secret-high-entropy-tokenSKILL.md:45High-entropy token-like string (may be an id, hash or a credential) (documentation table row)| 发票组件 | `ccIn…aux` |
table
Files scanned: 13. 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") - note
frontmatter-keyunknown frontmatter key "trigger_phrases"
Process rating: all ten parameters 49/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
- 30Running it twice. 3 mutating operations with no state check
- 70Execution cost. Instruction body is 4937 tokens
- 100Tools and files. No external tools needed
- 100Steps. 11 steps
- 100Consistency. Name and required fields are in place
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)
- +3Description length 88: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- -33 of 3 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +4Structure: 38 headings
- +3Step-by-step instructions: 11 items
- +4Has examples (42 code blocks)
- +4Reference files are cited in the instructions (3 of 7)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 69.