BF smyx-child-outdoor-activity-monitor-analysis
Using a fixed camera at the balcony door or home entrance, the system detects how many times the child enters/exits the home or balcony. With person-tracking and region-entry/exit logic, it records the timestamps of each 'leaving indoor (outdoor)' and 'returning indoor' event, and accumulates the daily total outdoor-activity duration. | 通过家庭阳台门或入户门口的固定摄像头，检测儿童进出家门或阳台的次数，利用人体跟踪和区域进出判定技术，记录每次离开室内（外出）和返回室内（归来）的时间点，累计每日户外活动总时长。当当日总时长低于预设推荐值（默认建议学龄儿童每天至少1小时户外活动）时，输出'户外活动不足'提醒，建议家长带孩子增加户外时间。
Using a fixed camera at the balcony door or home entrance, the system detects how many times the child enters/exits the home or balcony.
As a process F 32/100 · Will not run — 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 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 1669 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 490: 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.