AC retail-sku-store-analysis
单SKU门店分析工具。分析单个商品在指定门店的销售表现、库存状态、导购贡献和AIoT转化数据。 核心能力： 1. SKU基础信息（名称、款号、颜色、包型、标准价、上市日期） 2. 销售表现（销售额、销量、成交均价、贡献率、排名） 3. 库存状态（当前库存、在架天数、绑定状态） 4. 导购贡献（各导购销售额、销量、连带率、成交客户数） 5. AIoT转化数据（试用次数、成交件数、转化率） 触发条件： - 用户询问商品表现（如"心遥2卖得怎么样"） - 用户分析SKU数据（如"这个款库存还多吗"） - 用户需要导购贡献分析（如"谁卖了这款包"）
As a process C 53/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 · 0
✓ No critical or high findings
Files scanned: 3. 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 53/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
- 100Tools and files. No external tools needed
- 100Steps. 13 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1383 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
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- -216 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +5Description quotes 3 example trigger phrases
- +3Description length 275: enough signal without eating the budget
- +4Structure: 16 headings
- +3Step-by-step instructions: 13 items
- +4Has examples (5 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.