CD skill-compliance
Skill上架合规检查器（面向国内平台）。在上传前检查skill是否符合国内监管要求，包括金融敏感词、免责声明、安全红线等。
Skill上架合规检查器（面向国内平台）。在上传前检查skill是否符合国内监管要求，包括金融敏感词、免责声明、安全红线等。
As a process D 38/100 · Unfinished process — weak spots: steps, result and completion, when it triggers
What is at stake
The skill contains fragments that, in the wrong hands, cost money or data. Below: what the installer risks and what the author should do.
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
- Address the high-severity findings: each costs 18 safety points. If one is a false positive, add the rule id to guard.allow in spec.yaml.
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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
-
high Dangerous commands
cmd-pipe-to-shellCHANGELOG.md:23Downloads and executes remote code from an unrecognised host (pipe to shell)- **新增 SEC-005 外部脚本获取**：检测 curl|bash、wget|sh 等运行时外部代码获取模式
Medium and low: 1
-
low Dangerous commands
cmd-pipe-to-shellrules/skillhub-rules.json:1133Downloads and executes remote code from an unrecognised host (pipe to shell) (string literal in code, not executed; security demo / example)"description": "检测到从外部URL动态拉取并执行脚本的模式（curl|bash, wget|sh等）。这种运行时获取外部代码的行为存在供应链安全风险，攻击者可劫持URL指向恶意代码。建议将外部依赖打包在发布包中。",
code literaldemo
Files scanned: 14. 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 "use_when" - note
frontmatter-keyunknown frontmatter key "trigger_keywords" - note
frontmatter-keyunknown frontmatter key "environment" - note
frontmatter-keyunknown frontmatter key "network" - note
frontmatter-keyunknown frontmatter key "dependencies" - note
frontmatter-keyunknown frontmatter key "disclaimer"
Process rating: all ten parameters 38/100
- 0Steps. Prose only: no discrete steps
- 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
- 100Tools and files. No external tools needed
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 335 tokens
- 100Running it twice. No mutating operations
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 62: 120–800 characters recommended
- +3No numbered steps or checklist
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- -31 of 1 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +4Structure: 4 headings
Quality base 70; lint remarks subtract, signals add up to 100. Result: 56.