BD lanzou-downloader-0.0.5
蓝奏云下载器 v0.0.5，纯本地解析零第三方服务。一键下载蓝奏云单文件与文件夹分享（自动识别文件夹短码、自动处理 JS 反爬与密码验证、文件夹列表自动翻页、--select 选择性下载、大文件断流自动重试）。当用户发送蓝奏云分享链接（lanzou* / lanzn.com 域名）并表达下载意图时触发。不适用于其他网盘平台（百度网盘/阿里云盘/微云等）。
蓝奏云下载器 v0.0.5，纯本地解析零第三方服务。一键下载蓝奏云单文件与文件夹分享（自动识别文件夹短码、自动处理 JS 反爬与密码验证、文件夹列表自动翻页、--select 选择性下载、大文件断流自动重试）。当用户发送蓝奏云分享链接（lanzou / lanzn.com…
As a process D 49/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 · 1
✓ No critical or high findings
Medium and low: 1
-
low Secrets in code
secret-password-literalscripts/download.js:702Hard-coded password / key literal (may be an example)password = positional[2] || null;
Files scanned: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - 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 (lanzou-downloader-0.0.5) differs from the folder (lanzou-downloader)
- 100Tools and files. No external tools needed
- 100Steps. 16 steps
- 100Execution cost. Instruction body is 577 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)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 178: enough signal without eating the budget
- +4Structure: 10 headings
- +3Step-by-step instructions: 16 items
- +4Has examples (2 code blocks)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 70.