BD smyx-trauma-stress-behavior-detection-analysis
Using fixed cameras in emergency shelters, the system analyzes video of disaster-affected crowds to detect typical acute stress reactions: stupor (prolonged motionless state with no response to external stimulation), tremor (involuntary shaking of body or limbs), unresponsiveness (no orientation or avoidance reaction to calls or sounds), and hypervigilance (frequent scanning of surroundings, startle reactions). | 通过应急避难所内的固定摄像头，分析受灾人群的行为视频，检测急性应激反应下的典型行为：木僵（长时间静止不动，对外界刺激无反应）、颤抖（身体或四肢不自主抖动）、无反应（对呼唤、声响等刺激没有定向或回避反应）以及过度警觉（频繁环顾四周、惊跳反应）。当检测到上述行为时，输出心理危机预警，提示现场心理救援团队及时介入，提供紧急心理支持，预防急性应激障碍或创伤后应激障碍。
Using fixed cameras in emergency shelters, the system analyzes video of disaster-affected crowds to detect typical acute stress reactions: stupor (prolonged…
As a process D 35/100 · Unfinished process — weak spots: steps, result and completion, when it triggers
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: 30. 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 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 2012 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
- -260 emoji in the instructions: noise for the model
- -32 of 4 scripts are never mentioned in SKILL.md
- +2Single-language instructions
- +3Description length 598: 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.