AF alibabacloud-sas-log-to-oss
Alicloud Service Scenario-Based Skill. Use for automating SLS (Log Service) log export to OSS (Object Storage) for cold storage archival. Triggers: "SLS", "OSS", "log export", "log shipping", "cold storage", "log archive", "Security Center log backup", "list LogStore", "view LogStore", "create export task", "delete export task", "stop export task", "start export task", "manage export task", "cleanup export task", "force delete export", "日志导出", "日志投递", "冷存储", "日志归档", "创建导出", "删除导出", "停掉导出", "暂停导出", "关闭导出", "停用导出", "终止导出", "启动导出", "查看导出", "列出导出", "清理导出".
Alicloud Service Scenario-Based Skill.
As a process F 50/100 · Will not run — References files that are not bundled: references/how-to-implement-by-common-sdk.md
How to improve
- 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 · 2
✓ No critical or high findings
Medium and low: 2
-
low Dangerous commands
cmd-privilegereferences/cli-installation-guide.md:37Privilege escalation / world-writable permissions (documentation of a security skill)sudo mv aliyun /usr/local/bin/
security skill -
low Dangerous commands
cmd-privilegereferences/cli-installation-guide.md:43Privilege escalation / world-writable permissions (documentation of a security skill)sudo mv aliyun /usr/local/bin/
security skill
Files scanned: 12. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 5509 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: references/how-to-implement-by-common-sdk.md
Process rating: all ten parameters 50/100
- 0Tools and files. 1 referenced file(s) missing: references/how-to-implement-by-common-sdk.md
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 35 mutating operations with no state check
- 40Result and completion. Does not say what the result is
- 50When it triggers. No condition that starts the skill
- 70Execution cost. Instruction body is 5509 tokens
- 85Steps. 21 steps, 2 vague phrases
- 100Failures and branches. 7 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 13 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (3 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
- +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
- +5Description quotes 14 example trigger phrases
- +3Description length 558: enough signal without eating the budget
- +4Structure: 24 headings
- +3Step-by-step instructions: 21 items
- +4Has examples (16 code blocks)
- +4Reference files are cited in the instructions (8 of 8)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 80.