BC qq-zone-photo-free
管理QQ空间相册。支持扫码登录、列出相册、浏览照片、上传照片。。支持扫码登录、列出相册、浏览照片、上传照片。触发关键词: 浏览照片, photo, zone, 列出相册, 空间相册, 支持扫码登录, 管理。开箱即用,无需复杂配置,支持中文交互与结构化输出。轻量级设计,低资源占用,适配云端与本地部署。
管理QQ空间相册。支持扫码登录、列出相册、浏览照片、上传照片。。支持扫码登录、列出相册、浏览照片、上传照片。触发关键词: 浏览照片, photo, zone, 列出相册, 空间相册, 支持扫码登录, 管理。开箱即用,无需复杂配置,支持中文交互与结构化输出。轻量级设计,低资源占用,适配云端与本地部署。
As a process C 51/100 · Has gaps — 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: 0. 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 "slug" - note
frontmatter-keyunknown frontmatter key "displayName" - note
frontmatter-keyunknown frontmatter key "summary" - note
frontmatter-keyunknown frontmatter key "tools"
Process rating: all ten parameters 51/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. 1 mutating operations with no state check
- 100Tools and files. Tools declared in frontmatter
- 100Steps. 20 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 807 tokens
- low 11 top-level sections: this looks like several domains in one skill
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 150: enough signal without eating the budget
- +4Structure: 27 headings
- +3Step-by-step instructions: 20 items
- +4Has examples (8 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 70.