SKILLEMALL.ai

AC retail-traffic-analysis

门店客流与转化漏斗分析工具。基于AIoT客户行为数据(customerFunnel + behaviorFunnel)。 核心能力: 1. 双漏斗结合分析(customerFunnel客户分层 + behaviorFunnel试用行为) 2. 五步分析法(获取数据→解析customerFunnel→解析behaviorFunnel→计算转化率→综合诊断) 3. 完整逻辑标注(每个转化率指标包含逻辑说明、计算公式、原因解释、计算过程) 4. 互斥桶模型验证(普通+潜在+意向+成交=有效客户) 5. 核心转化率指标(潜在→意向、意向→成交、试用→成交、深度→成交) 6. 人均指标(人均深度试用、人均成交件数) 触发条件: - 用户询问客流(如"客流怎么样") - 用户分析转化率(如"转化率下降原因") - 用户需要漏斗分析(如"客户转化情况")

ClawHub Agent Skills author: Xtechmerge.AI v1.0.0 MIT-0 3 files body ≈ 1 061 tokens Open the sourceclawhub.ai analyzed 3 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. 36 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1061 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 2 example trigger phrases
  • +3Description length 377: enough signal without eating the budget
  • +4Structure: 21 headings
  • +3Step-by-step instructions: 36 items
  • +4Has examples (11 code blocks)

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

External checks

ClawHub: suspicious
This skill is a read-only store traffic analysis tool, but it depends on an unreviewed local API client and can fetch store business data with unclear credential scope.
LLM: suspicious (high) · VirusTotal: · 29 May 2026