BF linkfox-shopee-store-shop
Shopee（虾皮）店铺信息与设置（与 linkfox-shopee-store-auth 同系列），经 /shopee/developerProxy 转发 Shopee Open API Shop 模块全部 9 个接口：get_shop_info、get_profile、update_profile、get_warehouse_detail、get_shop_notification、get_authorised_reseller_brand、get_br_shop_onboarding_info、get_shop_holiday_mode、set_shop_holiday_mode。当用户提到 Shopee 店铺信息、店铺资料、店铺名称、仓库地址、卖家通知、授权品牌、巴西 KYC、假期模式、holiday mode、get_shop_info 时触发。即使未明确提及"店铺信息"，只要涉及已授权 Shopee 店铺的资料查询或店铺设置，也应触发。
Shopee（虾皮）店铺信息与设置（与 linkfox-shopee-store-auth 同系列），经 /shopee/developerProxy 转发 Shopee Open API Shop 模块全部 9…
As a process F 43/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 43/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
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 42 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1393 tokens
- 100Running it twice. No mutating operations
- low 11 top-level sections: this looks like several domains in one skill
- 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
- +1No license
- +2Single-language instructions
- +3Description length 430: enough signal without eating the budget
- +4Structure: 17 headings
- +3Step-by-step instructions: 42 items
- +4Reference files are cited in the instructions (2 of 2)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 66.