BC linkfox-sif-asin-summary
使用SIF(搜索情报框架)数据分析ASIN的流量来源构成与曝光分布,覆盖本期/上期/新进/退出周期对比。当用户提到ASIN流量来源、流量结构分析、自然流量与付费流量占比、曝光得分拆解、周期对比、新进/退出流量词、竞品流量分析、SP广告关键词数量、品牌广告曝光、Amazon's Choice曝光、编辑推荐曝光、Top Rated曝光、视频广告曝光、自然搜索曝光比例、PPC流量来源、促销秒杀流量来源、推荐位结构拆解、ASIN traffic analysis, traffic sources, organic traffic share, ad traffic share, exposure analysis, traffic structure, period-over-period comparison, keyword churn, SIF时触发此技能。即使用户未明确提及"SIF",只要其需求涉及分析ASIN的流量来源、曝光渠道分布、跨周期对比或竞品流量结构对比,也应触发此技能。
As a process C 50/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 50/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
- 70Execution cost. Instruction body is 4156 tokens
- 100Steps. 46 steps
- 100Consistency. Name and required fields are in place
- 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 (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 447: enough signal without eating the budget
- +4Structure: 20 headings
- +3Step-by-step instructions: 46 items
- +4Has examples (2 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.