BF tencentcloud-cvm-skill
腾讯云 CVM 云服务器运维工具集
腾讯云 CVM 云服务器运维工具集
As a process F 32/100 · Will not run — References files that are not bundled: scripts/ops/*.sh
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The text references files that are not there: add them or drop the references.
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 · 5
✓ No critical or high findings
Medium and low: 5
-
low Dangerous commands
cmd-cron-mentionscripts/ops/remote-exec.sh:79Mentions editing / listing crontab (string literal in code, not executed)"crontab -l"
code literal -
low Dangerous commands
cmd-background-processscripts/ops/remote-exec.sh:125Starts a background / autostarted process (string literal in code, not executed)"systemctl enable"
code literal -
low Dangerous commands
cmd-cron-mentionscripts/ops/remote-exec.sh:243Mentions editing / listing crontab (string literal in code, not executed)echo " env, crontab -l, docker ps, docker images"
code literal -
low Dangerous commands
cmd-cron-mentionscripts/ops/security-check.sh:80Mentions editing / listing crontab (documentation of a security skill)crontab -l 2>/dev/null || echo "无"
security skill -
low Dangerous commands
cmd-cron-mentionSKILL.md:190Mentions editing / listing crontab (documentation table row)| | `crontab -l` | 定时任务列表 |
table
Files scanned: 32. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-shortdescription under 40 chars: too little signal for triggering - warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
missing-refreference to a missing file: scripts/ops/*.sh
Process rating: all ten parameters 32/100
Will not run. References files that are not bundled: scripts/ops/*.sh
- 0Tools and files. 1 referenced file(s) missing: scripts/ops/*.sh
- 0Result and completion. Does not say what the result is
- 0When it triggers. No condition that starts the skill
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 30Running it twice. 1 mutating operations with no state check
- 100Steps. 7 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1894 tokens
- 100Progress reporting. Reports progress
- low The response is described with custom markup (12 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)
- +3Description length 17: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- -41 reference files, but SKILL.md never points to them: the model will not open them
- +1No license
- +2Single-language instructions
- +4Structure: 20 headings
- +3Step-by-step instructions: 7 items
- +4Has examples (7 code blocks)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 54.