AC dlazy-ecommerce-main-image
电商爆款主图生成与编辑。上传已批准的商品图，生成搜索列表里能被认出、商品事实准确、卖点有画面证据、符合渠道规则的主图候选，并按单变量原则产出 A/B 测试组。覆盖白底基线图、可视差异图、内容电商场景图、配色 SKU 组、单变量背景测试五种场景，适用于淘宝天猫京东拼多多抖音小红书 Amazon TikTok Shop Shopify 的主图与首图。当用户需要「做主图」「爆款主图」「白底图」「主图测款」「测图」「A/B 测试主图」「一个 SKU 铺多个配色」时使用本技能。转化受价格、评价、库存与流量共同影响，图片不单独构成爆款保证。
电商爆款主图生成与编辑。上传已批准的商品图，生成搜索列表里能被认出、商品事实准确、卖点有画面证据、符合渠道规则的主图候选，并按单变量原则产出 A/B 测试组。覆盖白底基线图、可视差异图、内容电商场景图、配色 SKU 组、单变量背景测试五种场景，适用于淘宝天猫京东拼多多抖音小红书 Amazon TikTok Shop…
As a process C 57/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, running it twice
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 · 0
✓ No critical or high findings
Files scanned: 2. 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 57/100
- 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
- 30Running it twice. 1 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 100Steps. 27 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1903 tokens
- low 10 top-level sections: this looks like several domains in one skill
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)
- +1No license
- +2Single-language instructions
- +3Description length 267: enough signal without eating the budget
- +4Structure: 25 headings
- +3Step-by-step instructions: 27 items
- +3Output format is stated explicitly
- +4Has examples (12 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.