Health Sync Analysis Skill

Purpose

This skill is dedicated to analyzing the user's health data across available providers:

• Oura
• Withings
• Hevy
• Strava
• WHOOP
• Eight Sleep

Scope

Use this skill when the user asks questions such as:

• How did I sleep last night?
• How was my last workout?
• How did my resting heart rate change during the year?
• What trends are you seeing in my recovery, sleep, and training?
• What useful insights or next steps should I focus on?

Setup Handling (Remote Bootstrap Only)

Setup is bot-led and remote-first. The only supported onboarding flow is:

• Bot runs npx health-sync init remote bootstrap.
• Bot sends user: npx health-sync init --remote .
• User sends back encrypted archive.
• Bot runs npx health-sync init remote finish .

• references/setup.md

• health-sync init as the primary user instruction
• health-sync auth as a standalone onboarding path

Runtime And Data Disclosure (Mandatory)

This skill assumes the bot environment has local CLI and filesystem access.

• Required binary:
• node
• npm
• npx
• Expected local working paths:
• workspace/health-sync/health-sync.toml
• workspace/health-sync/.health-sync.creds
• workspace/health-sync/health.sqlite
• Sensitive-data handling:
• Remote onboarding imports encrypted archives that contain provider credentials/tokens.
• Finish flow writes decrypted secrets to local files on the bot host.
• These files must be treated as sensitive at rest (access controls, backups, retention).
• Chat-safety boundary:
• Never ask users to paste raw secrets in chat.
• Only collect encrypted archive files via remote bootstrap flow.

Schema Handling

To understand data schemas and query correctly, read the provider reference files:

• references/oura.md
• references/withings.md
• references/hevy.md
• references/strava.md
• references/whoop.md
• references/eightsleep.md

Freshness Rule (Mandatory)

Before any analysis, always run:

npx health-sync sync

If sync fails, report the failure clearly and continue analysis only if the user explicitly asks to proceed with potentially stale data.

Analysis Workflow

• Run npx health-sync sync first.
• Identify the user question and which provider/resource(s) are relevant.
• Read the provider schema reference before forming SQL.
• Query records, sync_state, and sync_runs as needed.
• Produce a clear, user-friendly answer with concrete numbers and dates.
• Highlight meaningful patterns and offer practical guidance.
• When data quality or coverage is limited, say so explicitly.

Output Style

• Be concise, clear, and practical.
• Focus on useful interpretation, not just raw data dumps.
• Connect metrics to actionable insights (sleep, recovery, training, consistency, etc.).
• Ask follow-up questions only when necessary to improve analysis quality.