Setup & Installation
Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:
Version History
# v0.3.5 ## Compare Range - v0.3.4..v0.3.5 ## Highlights - Fixed sync fsck consistency behavior across providers. - Fixed Hevy delta watermark parsing for updated events. - Added/expanded regression tests for sync state, provider watermarks, and stale-row handling. ## Diff Summary package-lock.json | 4 +- package.json | 2 +- release-notes/v0.3.1.md | 25 +++++ release-notes/v0.3.2.md | 39 ++++++++ release-notes/v0.3.3.md | 34 +++++++ release-notes/v0.3.4.md | 41 ++++++++ src/db.js | 197 ++++++++++++++++++++++++++++++++------- src/providers/hevy.js | 30 ++++-- src/providers/strava.js | 29 ++++-- src/providers/whoop.js | 29 ++++-- tests/db.test.js | 98 +++++++++++++++++++ tests/hevy-provider.test.js | 38 ++++++++ tests/provider-contracts.test.js | 2 +- tests/strava-provider.test.js | 70 +++++++++++++- tests/whoop-provider.test.js | 94 ++++++++++++++++++- 15 files changed, 667 insertions(+), 65 deletions(-) ## Changed Files - package-lock.json - package.json - release-notes/v0.3.1.md - release-notes/v0.3.2.md - release-notes/v0.3.3.md - release-notes/v0.3.4.md - src/db.js - src/providers/hevy.js - src/providers/strava.js - src/providers/whoop.js - tests/db.test.js - tests/hevy-provider.test.js - tests/provider-contracts.test.js - tests/strava-provider.test.js - tests/whoop-provider.test.js ## Full Changes - release: v0.3.5 (49d08d7) - Fix sync fsck consistency across providers (eadb00a) - Fix Hevy delta watermark parsing for updated events (e59df3c)
What This Skill Does
Pulls health data from multiple wearable and fitness platforms into a single SQLite database for cross-provider analysis. Lets an AI agent query sleep, recovery, training, and activity metrics through a unified CLI. Answers questions like "how did my sleep affect my workout performance last week" by correlating signals across devices.
Instead of checking five separate apps, this centralizes all health metrics into one queryable database so an agent can correlate signals across providers in a single conversation.
When to use it
- Comparing last night's sleep score from Oura against WHOOP recovery
- Tracking resting heart rate trends across months in Withings data
- Reviewing weekly training load from Strava and Hevy together
- Asking why recovery dropped after a travel week using Eight Sleep data
- Getting a cross-provider summary before a competition or event
Example Workflow
Here's how your AI assistant might use this skill in practice.
User asks: How was my recovery and sleep this week compared to last week?
- 1Run `npx health-sync sync` to fetch latest data from all connected providers
- 2Query the Oura and WHOOP records tables for sleep and recovery scores over the past 14 days
- 3Calculate weekly averages and identify any meaningful differences between the two weeks
- 4Check Strava and Hevy records to see if training load changed between the periods
- 5Present a comparison with concrete numbers and note any likely cause-effect relationships
A side-by-side weekly summary showing sleep scores, recovery percentages, and training load, with a plain-language explanation of what changed and why it may have happened.
Requirements
Accounts, API keys, or tools you or your AI assistant may need to set up while using this skill.