BF linkfox-shopee-store-ads
Shopee(虾皮)店铺站内广告 Ads(与 linkfox-shopee-store-auth 同系列),经 /shopee/developerProxy 转发 Shopee Open API Ads 模块 23 个接口:get_total_balance、create_manual_product_ads、get_product_campaign_daily_performance、GMS 广告等。调用前须确认目标店已有 appType=ad 授权(ERP 授权不能代替)。当用户提到 Shopee 广告、Ads、广告余额、CPC、商品推广、手动广告、campaign、广告效果、ROI、get_total_balance、广告授权 时触发。即使未明确提及"广告",只要涉及已授权 Shopee 店铺的广告账户、推广或效果查询,也应触发。
Shopee(虾皮)店铺站内广告 Ads(与 linkfox-shopee-store-auth 同系列),经 /shopee/developerProxy 转发 Shopee Open API Ads 模块 23…
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.
- 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 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. 19 mutating operations with no state check
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 47 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2041 tokens
- low 11 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
- +4No input/output examples
- -311 of 29 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 373: enough signal without eating the budget
- +4Structure: 16 headings
- +3Step-by-step instructions: 47 items
- +4Reference files are cited in the instructions (2 of 2)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 69.