SKILLEMALL.ai

BF smyx-elderly-gait-instability-detection-analysis

Using a fixed camera in a hallway or living room to record video of an elderly person walking in a straight line, AI pose estimation and gait analysis extract parameters such as step length (cm), gait speed (m/s), trunk sway angle (left-right tilt), and cadence to evaluate gait stability. | 通过走廊或客厅的固定摄像头拍摄老年人直线行走的视频,利用AI姿态估计和步态分析技术检测步幅长度(cm)、步速(m/s)、躯干摇摆角度(左右倾斜度)以及步频等参数,评估步态稳定性。当步幅过小(小碎步)、步速过慢、躯干摇摆幅度过大时,输出跌倒风险等级(低/中/高)。

ClawHub Agent Skills author: smyx-sunjinhui v1.0.9 MIT-0 30 files body ≈ 1 641 tokens Open the sourceclawhub.ai analyzed 4 d ago

As a process F 32/100 · Will not run — weak spots: steps, result and completion, when it triggers

AnalyzerInfrastructureMedia and videotype 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
F
32/100
Will not run
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 32/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
  • 30Running it twice. 1 mutating operations with no state check
  • 60Tools and files. Uses tools (python) that frontmatter does not declare
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1641 tokens

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
  • -257 emoji in the instructions: noise for the model
  • -32 of 4 scripts are never mentioned in SKILL.md
  • +2Single-language instructions
  • +3Description length 423: 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’s gait-analysis purpose is real, but it sends sensitive videos and identity-linked data to cloud services with unsafe defaults and under-disclosed persistence.
LLM: suspicious (high) · 9 Sept 2026