oscar-fitbit-integration

Integrate Fitbit data into OSCAR Export Analyzer with OAuth 2.0 PKCE.

Updated Sep 6, 2025
One-click install
npx skills add https://github.com/kabaka/oscar-export-analyzer --skill oscar-fitbit-integration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: oscar-fitbit-integration
Source: https://github.com/kabaka/oscar-export-analyzer/tree/main/.github/skills/oscar-fitbit-integration
Command: npx skills add https://github.com/kabaka/oscar-export-analyzer --skill oscar-fitbit-integration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill documents secure integration between OSCAR Export Analyzer and Fitbit Web API, detailing OAuth PKCE flows, encrypted token storage, and analytics-backed correlation of CPAP therapy data with heart rate, sleep and oxygen data.

Core Features & Use Cases

  • OAuth 2.0 with PKCE: End-to-end authorization code flow with PKCE to securely obtain access tokens for Fitbit data.
  • Token Encryption & Storage: End-to-end encryption of tokens and state to protect credentials in client storage.
  • API Worker for Data Fetching: Offload Fitbit API requests to a web worker to keep the UI responsive.
  • Correlation Analytics: Align CPAP session data with Fitbit metrics to enable cross‑domain insights.
  • Use Case: A clinician wants to correlate nightly CPAP usage with Fitbit heart rate and sleep stages for a complete patient view.

Quick Start

Authenticate with Fitbit using PKCE, then enable the API worker to fetch daily metrics and run correlation analyses on the combined CPAP and Fitbit data.

Frequently Asked Questions about oscar-fitbit-integration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I integrate Fitbit data with OSCAR using OAuth 2.0 PKCE?

Fitbit data integrates with OSCAR through an OAuth 2.0 PKCE authorization flow that securely obtains access tokens. The process enforces encrypted token storage and uses a dedicated API worker for non-blocking data retrieval.

Can I correlate CPAP therapy data with Fitbit heart rate and sleep metrics?

Correlating CPAP therapy data with Fitbit metrics aligns nightly CPAP sessions with heart rate, sleep stages, and oxygen data. This cross-domain analytics approach provides a complete patient view for clinicians evaluating therapy outcomes.

How does token encryption work for Fitbit API integration?

Token encryption secures Fitbit API credentials by applying end-to-end encryption to access tokens and OAuth state. This protects sensitive authentication data within client storage during CPAP and sleep data correlation workflows.

What is the best way to keep the UI responsive when fetching Fitbit Web API data?

Fetching Fitbit Web API data is kept responsive by offloading API requests to a dedicated web worker. This non-blocking data retrieval mechanism prevents UI freezes during sleep and heart rate metric correlation.

Do I need a dedicated API worker for Fitbit sleep data alignment?

A dedicated API worker is required for Fitbit sleep data alignment to ensure non-blocking API requests. It handles the OAuth-authenticated data retrieval process, keeping the OSCAR analyzer interface responsive during correlation.

Why use OAuth PKCE flow for Fitbit Web API integration?

OAuth PKCE flow secures Fitbit Web API integration by requiring a dynamic code verifier for each authorization request. This prevents interception attacks during token exchange when accessing sleep and heart rate data.