AD garmin-connect
读取 Garmin Connect 手表/设备数据。 触发场景： - "今天走了多少步" - "昨晚睡眠怎么样" - "最近有什么运动" - "心率怎么样" - "这周跑了多少次" - 查询任意日期的运动、睡眠、心率等健康数据
As a process D 41/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- 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: 7. 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 41/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
- 40Consistency. Frontmatter name (garmin-connect) differs from the folder (garmin-connect-cn)
- 60Tools and files. Uses tools (python) that frontmatter does not declare
- 100Steps. 5 steps
- 100Execution cost. Instruction body is 143 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)
- +3Description length 113: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- -31 of 2 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +5Description quotes 4 example trigger phrases
- +4Structure: 7 headings
- +3Step-by-step instructions: 5 items
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (1 of 2)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.
External checks
ClawHub: suspicious
This Garmin health-data skill mostly does what it says, but it handles a sensitive account token unsafely and includes a hard-coded Garmin user ID that could query the wrong account.
LLM: suspicious (high) · VirusTotal: · 29 May 2026