BF garmin-health-analysis
Talk to your Garmin data naturally - "what was my fastest speed snowboarding?", "how did I sleep last night?", "what was my heart rate at 3pm?". Access 20+ metrics (sleep stages, Body Battery, HRV, VO2 max, training readiness, body composition, SPO2), download FIT/GPX files for route analysis, query elevation/pace at any point, and generate interactive health dashboards. From casual "show me this week's workouts" to deep "analyze my recovery vs training load".
Talk to your Garmin data naturally - "what was my fastest speed snowboarding?", "how did I sleep last night?", "what was my heart rate at 3pm?". Access 20+…
As a process F 31/100 · Will not run — References files that are not bundled: references/mcp_setup.md, scripts/garmin_data.py, scripts/garmin_chart.py
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The text references files that are not there: add them or drop the references.
- 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: 0. 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") - warning
missing-refreference to a missing file: references/mcp_setup.md - warning
missing-refreference to a missing file: scripts/garmin_data.py - warning
missing-refreference to a missing file: scripts/garmin_chart.py - warning
missing-refreference to a missing file: references/health_analysis.md - warning
missing-refreference to a missing file: references/api.md - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 31/100
- 0Tools and files. 5 referenced file(s) missing: references/mcp_setup.md, scripts/garmin_data.py, scripts/garmin_chart.py
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 2 mutating operations with no state check
- 40Consistency. Frontmatter name (garmin-health-analysis) differs from the folder (garmin-health-analysis-2)
- 50Failures and branches. 0 branches, has a failure section
- 85Steps. 57 steps, 1 vague phrases
- 100Execution cost. Instruction body is 2864 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 12 top-level sections: this looks like several domains in one skill
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)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +5Description quotes 5 example trigger phrases
- +3Description length 464: enough signal without eating the budget
- +4Structure: 30 headings
- +3Step-by-step instructions: 57 items
- +4Has examples (11 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 64.