CF k3s-deploy
自动化部署 K3s Kubernetes 集群到多台 Linux 服务器。支持自动镜像拉取、网络配置检测、CNI 插件安装。使用场景：(1) 从零部署 K3s 集群，(2) 修复 NotReady 节点，(3) 批量部署多节点集群。触发条件：用户提到 K3s、Kubernetes 部署、集群安装、节点加入等。
As a process F 35/100 · Will not run — References files that are not bundled: scripts/check-cluster.sh
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 instructions or scripts send data out: environment variables, keys, file contents, chat history. You may never notice, because the agent performs the upload as "part of the task".
If the upload is not needed for the task, remove it: catalogs flag such skills and delist them. If it is needed, name the destination explicitly, say what leaves the machine, and give the user a switch.
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.
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.
- 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
-
medium Exfiltration
net-credential-usescripts/deploy-k3s.sh:98Credential used in a network call (verify the destination is the intended service)ssh_exec $host $user $pass "curl -sfL https://get.k3s.io | sh -s - server \
-
medium Dangerous commands
cmd-pipe-to-shellscripts/deploy-k3s.sh:98Downloads and executes remote code from an unrecognised host (pipe to shell) (quoted — discussed, not commanded)ssh_exec $host $user $pass "curl -sfL https://get.k3s.io | sh -s - server \
quoted -
medium Exfiltration
exfil-read-secret-filesscripts/deploy-k3s.sh:112Reads credential / secret files (quoted — discussed, not commanded)ssh_exec $host $user $pass "mkdir -p ~/.kube && cp /etc/rancher/k3s/k3s.yaml ~/.kube/config && \
quoted -
medium Exfiltration
net-credential-usescripts/deploy-k3s.sh:134Credential used in a network call (verify the destination is the intended service)ssh_exec $host $user $pass "curl -sfL https://get.k3s.io | sh -s - agent \
-
medium Dangerous commands
cmd-pipe-to-shellscripts/deploy-k3s.sh:134Downloads and executes remote code from an unrecognised host (pipe to shell) (quoted — discussed, not commanded)ssh_exec $host $user $pass "curl -sfL https://get.k3s.io | sh -s - agent \
quoted
Files scanned: 5. 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
missing-refreference to a missing file: scripts/check-cluster.sh
Process rating: all ten parameters 35/100
- 0Tools and files. 1 referenced file(s) missing: scripts/check-cluster.sh
- 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
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 2 mutating operations with no state check
- 100Steps. 19 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 380 tokens
- 100Progress reporting. Reports progress
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
- +1No license
- +2Single-language instructions
- +3Description length 155: enough signal without eating the budget
- +4Structure: 16 headings
- +3Step-by-step instructions: 19 items
- +4Has examples (4 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
- +3All 2 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 73.