AD amazon-deep-research-v4
亚马逊深度选品V4：多平台交叉验证(AMZScout+西柚找词+卖家精灵) → 1688以图搜图同款采购 → 实时汇率7项毛利计算 → WIPO IP合规审计 → HTML可视化报告。 触发词：亚马逊调研/选品/市场调研/Amazon research/毛利分析/快速调研/产品分析/竞品分析/选品报告
As a process D 46/100 · Unfinished process — 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.
For the model run — optional
- 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: 11. 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 46/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 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
- 60Tools and files. Uses tools (python) that frontmatter does not declare
- 100Steps. 44 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1276 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)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 151: enough signal without eating the budget
- +4Structure: 12 headings
- +3Step-by-step instructions: 44 items
- +4Has examples (11 code blocks)
- +4Reference files are cited in the instructions (5 of 7)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 76.
External checks
ClawHub: suspicious
This skill appears purpose-aligned for marketplace research, but it asks the agent to extract and reuse live SellerSprite session cookies and tokens, which puts account access at risk.
LLM: suspicious (high) · VirusTotal: · 29 May 2026