BB linkfox-geekbi-temu-product
使用 GeekBI 查询 Temu 公开市场商品。用户显式提到 GeekBI、linkfox-geekbi-temu-product,或需要 goodsId 详情、最近 30 天历史、供货价、库存、日/周/月销量与销售额及增长等 GeekBI 差异字段时触发。仅按关键词、品类、价格、评分、销量或销售额进行通用商品筛选时使用 linkfox-temu-product-query;除非用户明确要求跨数据源对比,不要同时调用两条付费商品数据 skill。
使用 GeekBI 查询 Temu 公开市场商品。用户显式提到 GeekBI、linkfox-geekbi-temu-product,或需要 goodsId 详情、最近 30 天历史、供货价、库存、日/周/月销量与销售额及增长等 GeekBI…
As a process B 65/100 · Nearly there — weak spots: inputs and preconditions, running it twice, progress reporting
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:50High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)or "eyJh…iJ9")
quoted
Files scanned: 8. 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 65/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 1 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (web, python) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 100Steps. 50 steps
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2647 tokens
- low 10 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (10 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)
- -31 of 5 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 226: enough signal without eating the budget
- +4Structure: 26 headings
- +3Step-by-step instructions: 50 items
- +3Output format is stated explicitly
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (2 of 2)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 76.