SKILLEMALL.ai

BD smyx-driver-head-pose-abnormality-analysis

Using an in-cabin DMS camera, the system analyzes the driver's head pose in real time, computing head pitch (down/up) and yaw (left/right turn). | 通过车载DMS摄像头实时分析驾驶员头部姿态,计算头部俯仰角(低头/抬头)和偏航角(左/右转头)。当低头角度超过阈值(默认>30°)且持续时间超过2秒(可能为看手机、查看物品),或侧视角度超过阈值(默认>45°)持续时间超过2秒(可能为与乘客聊天、看窗外)时,输出分心驾驶预警,联动语音提醒,预防交通事故。

ClawHub Agent Skills author: smyx-skills v1.0.10 MIT-0 30 files body ≈ 1 623 tokens Open the sourceclawhub.ai analyzed 2 d ago

As a process D 35/100 · Unfinished process — weak spots: steps, result and completion, when it triggers

AnalyzerInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
B
88/100
safety, quality, tests
Safety 60%
100
Quality 40%
69
Run on models
none yet
Process rating
D
35/100
Unfinished process
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: 30. 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 35/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
  • 25Steps. 1 steps
  • 60Tools and files. Uses tools (python) that frontmatter does not declare
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1623 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)
  • +3No numbered steps or checklist
  • +3Output format is not stated: the model decides each time
  • -255 emoji in the instructions: noise for the model
  • -32 of 4 scripts are never mentioned in SKILL.md
  • +2Single-language instructions
  • +3Description length 299: enough signal without eating the budget
  • +4Structure: 19 headings
  • +4Has examples (3 code blocks)
  • +4Reference files are cited in the instructions (1 of 1)
  • +1License stated

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

External checks

ClawHub: suspicious
The skill can perform driver head-pose analysis, but it also silently creates or reuses cloud identity state, uploads sensitive driver media, queries history, and stores tokens locally without enough user control.
LLM: suspicious (high) · 27 Aug 2026