BC linkfox-expert-blue-ocean-market-scanner
亚马逊蓝海品类市场扫描专家。适用于用户提供品类关键词或 ASIN 后,需要多源市场洞察、关键词验证、趋势分析、竞争格局扫描、Top ASIN 拆解、利润核算或 HTML 品类报告的场景。
亚马逊蓝海品类市场扫描专家。适用于用户提供品类关键词或 ASIN 后,需要多源市场洞察、关键词验证、趋势分析、竞争格局扫描、Top ASIN 拆解、利润核算或 HTML 品类报告的场景。
As a process C 51/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 Secrets in code
secret-high-entropy-tokenskills/linkfox-jiimore-get-niche-info-by-keyword/scripts/onboarding.py:49High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)or "eyJh…iJ9")
quoted
A further 2 matches are quotations in this security skill's documentation and are not counted as findings.
Files scanned: 5. 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") - note
frontmatter-keyunknown frontmatter key "zh_name"
Process rating: all ten parameters 51/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
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (python) that frontmatter does not declare
- 100Steps. 37 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1178 tokens
- 100Running it twice. No mutating operations
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)
- +3Description length 93: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +4Structure: 7 headings
- +3Step-by-step instructions: 37 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 64.