CD vehicle-license-recognition-and-extract
基于来也科技ADP平台的中国机动车行驶证智能识别与信息抽取Skill。支持行驶证正副页全量字段的精准抽取——号牌号码、车辆类型、所有人、住址、使用性质、品牌型号、车辆识别代号VIN、发动机号码、注册日期、发证日期等20+关键字段，输出结构化JSON，零配置开箱即用，适用于车辆登记、保险投保、网约车/货运车辆准入等场景。
As a process D 49/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
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 · 4
-
high Dangerous commands
cmd-pipe-to-shellskill-card.md:24Downloads and executes remote code from an unrecognised host (pipe to shell)Risk: The skill documents curl|bash and irm|iex installation paths. <br>
Medium and low: 3
-
medium Dangerous commands
cmd-pipe-to-shell-known-hostREADME-CN.md:29Pipe-to-shell installer from a well-known host (still executes remote code)curl -fsSL https://raw.githubusercontent.com/laiye-ai/adp-cli/main/scripts/adp-init.sh | bash
-
medium Dangerous commands
cmd-pipe-to-shell-known-hostREADME.md:30Pipe-to-shell installer from a well-known host (still executes remote code)curl -fsSL https://raw.githubusercontent.com/laiye-ai/adp-cli/main/scripts/adp-init.sh | bash
-
medium Dangerous commands
cmd-pipe-to-shell-known-hostSKILL.md:63Pipe-to-shell installer from a well-known host (still executes remote code)curl -fsSL https://raw.githubusercontent.com/laiye-ai/adp-cli/main/scripts/adp-init.sh | bash
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")
Process rating: all ten parameters 49/100
- 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
- 40Consistency. Frontmatter name (vehicle-license-recognition-and-extract) differs from the folder (adp-vehicle-license-recognition-and-extract)
- 100Tools and files. No external tools needed
- 100Steps. 22 steps
- 100Execution cost. Instruction body is 3114 tokens
- 100Running it twice. No mutating operations
- low 12 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (4 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
- +2Single-language instructions
- +3Description length 160: enough signal without eating the budget
- +4Structure: 31 headings
- +3Step-by-step instructions: 22 items
- +4Has examples (17 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 73.