BC linkfox-junglescout-product-database
Jungle Scout产品数据库多条件筛选,支持按品类、价格、销量、收入、评论、评分、重量、BSR排名、LQS、卖家类型等维度筛选亚马逊商品,覆盖10个站点。当用户提到亚马逊选品、产品数据库筛选、BSR排名筛选、品类选品、高评分低竞争选品、FBA选品、亚马逊商品搜索、产品筛选、Amazon product database, product research, product filtering, BSR rank filter, category product search, niche product finder, FBA product search, Amazon product discovery, low competition products, Jungle Scout product database时触发此技能。即使用户未明确提及"Jungle Scout"或"产品数据库",只要其需求涉及按多条件筛选亚马逊商品或发现潜力产品,也应触发此技能。
As a process C 52/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 · 3
✓ No critical or high findings
Medium and low: 3
-
low Dangerous commands
cmd-shell-rcreferences/onboarding.md:13Writes to a shell startup file (quoted — discussed, not commanded)- macOS zsh:`echo 'export LINKFOX_AGENT_API_KEY="<key>"' >> ~/.zshrc && source ~/.zshrc`
quoted -
low Dangerous commands
cmd-shell-rcreferences/onboarding.md:14Writes to a shell startup file (detector / deny-list definition)- Linux bash:`echo 'export LINKFOX_AGENT_API_KEY="<key>"' >> ~/.bashrc && source ~/.bashrc`
detector -
low Secrets in code
secret-high-entropy-tokenscripts/onboarding.py:49High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)or "eyJh…iJ9")
quoted
Files scanned: 6. 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 52/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (python) that frontmatter does not declare
- 60Failures and branches. 2 branches
- 100Steps. 43 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1950 tokens
- 100Running it twice. No mutating operations
- 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 440: enough signal without eating the budget
- +4Structure: 15 headings
- +3Step-by-step instructions: 43 items
- +4Has examples (6 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.