SKILLEMALL.ai

AC retail-deal-goods-profile-analysis

成交商品画像分析工具。分析成交商品的品类、价格带、颜色、包型、上市时间等特征分布及环比变化。 核心能力: 1. 品类分布(女包/男包/钱包/配饰占比) 2. 价格带分布(主销价格带、高客单占比) 3. 包型分布(手提/斜挎/双肩/托特等) 4. 颜色分布(黑色系/棕色系/红色等) 5. 上市时间分布(新品/当季/老款占比) 6. 环比变化分析(本期vs上期特征变化) 触发条件: - 用户询问商品画像(如"成交商品有什么特征") - 用户分析品类结构(如"什么品类卖得好") - 用户需要价格带分析(如"主销价格带是多少")

ClawHub Agent Skills author: Xtechmerge.AI v1.0.0 MIT-0 3 files body ≈ 119 tokens Open the sourceclawhub.ai analyzed 4 d ago

As a process C 53/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions

AnalyzerInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
A
91/100
safety, quality, tests
Safety 60%
100
Quality 40%
77
Run on models
none yet
Process rating
C
53/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten

How to improve

  1. 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: 3. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description 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. 7 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 119 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
  • +1No license
  • +2Single-language instructions
  • +5Description quotes 3 example trigger phrases
  • +3Description length 265: enough signal without eating the budget
  • +4Structure: 6 headings
  • +3Step-by-step instructions: 7 items
  • +4Has examples (1 code blocks)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 77.

External checks

ClawHub: suspicious
This retail analytics skill appears purpose-aligned, but it should be reviewed because it loads an undeclared local API client outside the package to access store BI data.
LLM: suspicious (high) · VirusTotal: · 29 May 2026