CF alibabacloud-dataworks-datastudio-develop
DataWorks data development Skill. Create, configure, validate, deploy, update, move, and rename nodes and workflows. Manage components, file resources, and UDF functions. Covers 150+ node types: Shell, SQL, Python, DI, Flink, EMR, etc. Supports scheduled and manual workflow orchestration via aliyun CLI or Python SDK. WARNING: Supports mutating operations (Move, Rename) requiring explicit user confirmation. Delete operations are NOT supported by this skill. Triggers: DataWorks, data development nodes, workflows, FlowSpec, scheduling tasks, data integration, ETL pipelines, .spec.json. Also triggers for Alibaba Cloud data development, scheduling node configuration, FlowSpec format, or DI task orchestration.
As a process F 53/100 · Will not run — References files that are not bundled: references/workflow-guide.md, references/deploy-guide.md, references/nodetypes/index.md
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.
Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The skill tells the agent to hide things from you: not to show errors, not to mention actions, to report differently from what was done. You lose the ability to see what the agent really did.
Transparency beats a smooth answer. If the goal is to hide technical noise, ask the agent to "summarise briefly", not to "not mention".
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- The text references files that are not there: add them or drop the references.
- 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 · 3
✓ No critical or high findings
Medium and low: 3
-
medium Dangerous commands
cmd-pipe-to-shellSKILL.md:32Downloads and executes remote code from an unrecognised host (pipe to shell) (quoted — discussed, not commanded)> run `curl -fsSL --connect-timeout 10 --max-time 120 https://aliyuncli.alicdn.com/setup.sh | bash` to update,
quoted -
medium Concealment
en-hide-from-userSKILL.md:396Instruction to hide actions from the user (security demo / example)15. **Never claim deployment success unless `Pipeline.Status == 'Success'`**: After `create-pipeline-run`, the only outcome that means "deployed" is a final `Pipeline.Status` of `Success` returned by
demo -
low Dangerous commands
cmd-autorun-instructionreferences/acceptance-criteria.md:375Instructs the agent to auto-run a script on every session (negated — the text forbids it)5. **Do not skip validation**: Always run validate.py after each modification
negated
Files scanned: 80. 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") - warning
body-longSKILL.md body ≈ 10842 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: references/workflow-guide.md - warning
missing-refreference to a missing file: references/deploy-guide.md - warning
missing-refreference to a missing file: references/nodetypes/index.md - warning
missing-refreference to a missing file: references/troubleshooting.md - warning
missing-refreference to a missing file: references/api/UpdateComponent.md - warning
missing-refreference to a missing file: references/api/UpdateNode.md - warning
missing-refreference to a missing file: references/api/RenameNode.md - warning
missing-refreference to a missing file: references/api/UpdateWorkflowDefinition.md - warning
missing-refreference to a missing file: references/api/MoveWorkflowDefinition.md - warning
missing-refreference to a missing file: references/api/RenameWorkflowDefinition.md - warning
missing-refreference to a missing file: references/api/UpdateResource.md - warning
missing-refreference to a missing file: references/api/RenameResource.md - warning
missing-refreference to a missing file: references/api/UpdateFunction.md - warning
missing-refreference to a missing file: references/api/RenameFunction.md - warning
missing-refreference to a missing file: references/related-apis.md - warning
missing-refreference to a missing file: references/ram-policies.md - warning
missing-refreference to a missing file: references/verification-method.md - warning
missing-refreference to a missing file: references/cli-installation-guide.md - warning
missing-refreference to a missing file: references/flowspec-guide.md - warning
missing-refreference to a missing file: references/scheduling-guide.md - warning
missing-refreference to a missing file: references/di-guide.md - warning
missing-refreference to a missing file: references/nodetypes/{category}/{TYPE}.md - warning
missing-refreference to a missing file: references/nodetypes/data_integration/DI.md - warning
missing-refreference to a missing file: references/api/{APIName}.md
Process rating: all ten parameters 53/100
- 0Tools and files. 24 referenced file(s) missing: references/workflow-guide.md, references/deploy-guide.md, references/nodetypes/index.md
- 0Inputs and preconditions. Does not say what the process needs to start
- 40Result and completion. Does not say what the result is
- 40Execution cost. Instruction body is 10842 tokens: crowds the task out of the window
- 50When it triggers. No condition that starts the skill
- 100Steps. 88 steps
- 100Failures and branches. 27 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low The response is described with custom markup (7 tags): a typed call is more reliable
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
- -220 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +3Description length 713: enough signal without eating the budget
- +4Structure: 25 headings
- +3Step-by-step instructions: 88 items
- +4Has examples (12 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 52.