BC linkfox-seerfar-ozon-product-detail-search
Seerfar Ozon 商品详情查询：按 Ozon 商品 SKU 拉取单个商品的完整详情，返回标题、价格（卢布）、评分、评论数、QA数、统计窗口内总销量与日均销量、销售额、库存、类目排名、每日销量趋势、品牌、卖家、配送方式（FBO/FBS/OZON）、重量、上架时间/天数/月数等。用于单品深度分析、竞品商品拆解、Ozon 选品评估、Listing 诊断、销量趋势与类目排名跟踪。当用户提到 Ozon 商品详情、Ozon 单品分析、Ozon SKU 查询、竞品商品数据、Ozon 销量趋势、Ozon 类目排名、Ozon 库存、Ozon 上架时间、Seerfar Ozon 商品搜索、Ozon product detail, Ozon SKU lookup, single product analysis, competitor product teardown, Ozon sales trend, category rank 时触发此技能。即使用户未明确提到"Seerfar"，只要其意图是查看某个 Ozon 商品的详细数据，也应触发此技能。
Seerfar Ozon 商品详情查询：按 Ozon 商品 SKU…
As a process C 58/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: 1. 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 58/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 20When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (web, python) that frontmatter does not declare
- 100Steps. 38 steps
- 100Failures and branches. 3 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2308 tokens
- 100Running it twice. No mutating operations
- 100Progress reporting. Reports progress
- low 10 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (7 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
- -31 of 2 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 474: enough signal without eating the budget
- +4Structure: 12 headings
- +3Step-by-step instructions: 38 items
- +4Has examples (4 code blocks)
- +4Reference files are cited in the instructions (2 of 2)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 73.