BF linkfox-shopee-store-shop-category
Shopee（虾皮）店铺分类 Shop Category（与 linkfox-shopee-store-auth 同系列），经 /shopee/developerProxy 转发 Shopee Open API Shop Category 模块全部 7 个接口：add_shop_category、get_shop_category_list、update_shop_category、add_item_list、get_item_list、delete_item_list 等。当用户提到 Shopee 店铺分类、Shop Category、自定义分类、add_shop_category、shop_category_id、分类商品 时触发。即使未明确提及"分类"，只要涉及已授权 Shopee 店铺的 Shop Category 管理，也应触发。
Shopee（虾皮）店铺分类 Shop Category（与 linkfox-shopee-store-auth 同系列），经 /shopee/developerProxy 转发 Shopee Open API Shop Category 模块全部 7…
As a process F 40/100 · Will not run — References files that are not bundled: references/apis/
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The text references files that are not there: add them or drop the references.
- 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") - warning
missing-refreference to a missing file: references/apis/
Process rating: all ten parameters 40/100
- 0Tools and files. 1 referenced file(s) missing: references/apis/
- 0Result and completion. Does not say what the result is
- 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. 10 mutating operations with no state check
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 19 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 876 tokens
- low The response is described with custom markup (8 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
- +4No input/output examples
- -34 of 13 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 375: enough signal without eating the budget
- +4Structure: 12 headings
- +3Step-by-step instructions: 19 items
- +4Reference files are cited in the instructions (2 of 2)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 63.