AD webprinter-skill
调用官方 WebPrinter 云打印服务（webprinter.cn），提供企业智慧文印、打印管控、共享打印、 远程打印等全套打印管理功能，此技能的能力包含查询打印机、上传本地文件、创建漫游打印任务、 直接打印到指定设备，以及分别更新单双面、颜色、份数和纸张等打印参数。使用前需要先安装咱丢打印服务， 参考 [https://liqdopokb8.feishu.cn/docx/A0audnVIaoolXqxWUHPcvl1UnFd](https://liqdopokb8.feishu.cn/docx/A0audnVIaoolXqxWUHPcvYlUnFd ) 如果只是要向本地网络打印机提交打印，可使用云上驱动打印([https://github.com/zimsoft/cloud-driver-print/](https://github.com/zimsoft/cloud-driver-print/))。
As a process D 39/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- 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 · 0
✓ No critical or high findings
Files scanned: 7. 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 "env_vars"
Process rating: all ten parameters 39/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
- 30Running it twice. 3 mutating operations with no state check
- 40Consistency. Frontmatter name (webprinter-skill) differs from the folder (webprinter)
- 60Tools and files. Uses tools (python) that frontmatter does not declare
- 100Steps. 101 steps
- 100Execution cost. Instruction body is 1791 tokens
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 409: enough signal without eating the budget
- +4Structure: 24 headings
- +3Step-by-step instructions: 101 items
- +4Has examples (24 code blocks)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 74.