Fitbit Connector Skill (Tool Provider)

Use this skill when OpenClaw needs Fitbit or unified health data.

This is the canonical front door for health / Fitbit retrieval in OpenClaw.
If a user asks for latest Fitbit numbers, recovery signals, readiness trends, sleep/HRV/resting-HR patterns, or recent health metrics for training interpretation, start here.

This skill is data-plane only:

• - it authenticates,
• fetches Fitbit data,
• syncs/cache stores normalized metrics,
• returns compact JSON.

OpenClaw handles interpretation, decisions, and coaching language.

Canonical usage rule

For ordinary question-answering, prefer this skill first.
Do not start by searching the workspace for Fitbit paths if this skill is available.
Do not prefer older opinionated helper scripts over this interface.

For training questions, combine this skill with memory/training-continuity.md:

• - this skill = latest health/recovery data
• INLINECODE1 = training state, progression rules, recent workout context

Setup

1. 1. Create Fitbit developer app (type Personal).
2. Redirect URI: http://127.0.0.1:8787/callback.
3. Create .env from references/env.example.
4. Run auth bootstrap:

Primary front-door interface (recommended)

For most OpenClaw usage, call the narrow front door first:

• - INLINECODE10

This keeps retrieval typed and low-ambiguity.

Backend tool interface (compact JSON)

Direct backend contract/schema:

• - INLINECODE11
• Auth status:

• - Endpoint catalog (broad API surface):

• - Capability discovery across last N days (rate-limit aware):

• - Direct Fitbit endpoint fetch (generic exposure):

• - Fetch API day payload:

• - Fetch cached date range (field-filtered):

• - Fetch latest N cached days:

• - Sync one day from Fitbit API to cache:

• - Sync date range from Fitbit API to cache:

• - Query sync quality flags:

• - Unified DB status (Apple + Fitbit):

• - Unified latest daily rows with source preference:

Canonical QA patterns

Latest Fitbit / recovery snapshot

• - "What do my latest Fitbit numbers suggest?"
• "How does recovery look today?"
• "Give me my newest HRV / sleep / resting HR"

Prefer:

• - INLINECODE27

Unified health snapshot

• - INLINECODE28

Trend / confidence checks

• - INLINECODE29

Training interpretation

• - "Should I train today?"
• "How did yesterday compare to recovery?"
• "Has recovery improved since earlier this week?"

Use both:

1. 1. this skill for current/recent health signals
2. INLINECODE30 for training rules, progression, and recent exercise context

Notes

• - Output contract: compact JSON (machine-optimized, minimal token usage).
• Prefer narrow --metrics lists to keep token usage low.
• SQLite cache is local reliability layer; Fitbit API remains source-of-truth.
• No medical diagnosis. This skill only provides data.

Anti-patterns

If this skill is available, avoid these failure modes:

• - searching the workspace first just to locate Fitbit functionality
• asking the user where the connector lives
• preferring fitbit_query.py over fitbit_tools.py for normal QA
• treating memory references as the primary source of live Fitbit data
• using orchestrator files as the first discovery surface for ordinary health questions

Legacy scripts

Older opinionated scripts remain only for backward compatibility and should be treated as non-canonical for ordinary OpenClaw reasoning:

• - INLINECODE34
• INLINECODE35

If a normal user question can be answered through fitbit_tools.py, do that instead.