BC guaikei-kuaishou-open-data-fetcher
抓取快手公开数据：按关键词搜视频、拉博主作品列表、取视频评论，返回结构化 JSON。当任务涉及快手数据、快手爬虫、视频搜索或评论采集时使用。Kuaishou data fetcher: search videos, list creator posts, fetch comments. | 143 | 动词开头（命令式）+ 高频搜索词全前置
抓取快手公开数据：按关键词搜视频、拉博主作品列表、取视频评论，返回结构化 JSON。当任务涉及快手数据、快手爬虫、视频搜索或评论采集时使用。Kuaishou data fetcher: search videos, list creator posts, fetch comments.
As a process C 53/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: 22. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 2, column 14: description: 抓取快手公开数据：按关键词搜视频、拉博主作品列表、取视频评论，返回结构化 JSON。当任务涉及快手数据、快手爬虫、视频搜索或评论采集… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 53/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
- 100Tools and files. No external tools needed
- 100Steps. 52 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1041 tokens
- 100Running it twice. No mutating operations
- low 12 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
- +4No input/output examples
- +2Single-language instructions
- +3Description length 171: enough signal without eating the budget
- +4Structure: 16 headings
- +3Step-by-step instructions: 52 items
- +4Reference files are cited in the instructions (2 of 2)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 63.