Setup & Installation
Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:
Version History
Hardened auth/config handling: removed implicit env fallbacks, moved to explicit CLI flags for credentials/config, added required runtime bins metadata, and aligned docs/messages with behavior.
What This Skill Does
Rebuilds and maintains garmin_tracking.json by scraping Garmin Connect for activity history and training plan data. The start date is fixed at 2026-02-01, and all activity data is normalized into a canonical schema with fields like distanceKm, durationSec, and avgHrBpm.
Automates the full rebuild cycle from browser session reuse to schema validation, so no manual Garmin export or data wrangling is needed.
When to use it
- Syncing Garmin run history after completing a training week
- Refreshing upcoming training plan weeks in a local JSON file
- Rebuilding garmin_tracking.json after schema changes or data corruption
- Validating canonical activity fields across a full training history
- Tracking cumulative training summary from a fixed control start date
Example Workflow
Here's how your AI assistant might use this skill in practice.
User asks: Sync my Garmin training data and rebuild the tracking file
- 1Opens Garmin activities list page and collects all activities from 2026-02-01 onward
- 2Opens Garmin training plan page to refresh currentWeek and upcoming fields
- 3Rebuilds history array with canonical activity shape (type, distanceKm, durationSec, avgPaceSecPerKm, avgHrBpm, calories, sourceId)
- 4Recomputes summary totals and sets summary.to to today's date
- 5Runs reconcile_tracking.py to validate the schema and write the final file
garmin_tracking.json updated with current activity history, recomputed summary, and refreshed upcoming training plan
Requirements
Accounts, API keys, or tools you or your AI assistant may need to set up while using this skill.