integrate-cgm-data-source

Automate CGM data source integration into T1D Companion with schema and API changes.

Updated May 15, 2026

Search Tags:#database schema #API development #data integration #CGM #Python automation

Ready to run

npx skills add https://github.com/ruskibeats/t1d --skill integrate-cgm-data-source

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: integrate-cgm-data-source
Source: https://github.com/ruskibeats/t1d/tree/main/.pi/skills-archive/integrate-cgm-data-source
Command: npx skills add https://github.com/ruskibeats/t1d --skill integrate-cgm-data-source

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the process of integrating new continuous glucose monitor (CGM) data sources into the T1D Companion, reducing the complexity of onboarding new glucose providers.

Core Features & Use Cases

CGM Data Integration: Add support for new glucose providers like Dexcom, Nightscout, LibreLinkUp, Medtronic, or Eversense.
Database Configuration: Automate the addition of new fields to the user database model for storing CGM connection credentials and status.
API Service Class Creation: Generate the necessary API service class to interact with external CGM APIs.
Sync and Deduplication: Implement data sync from external sources to the T1D Companion database with deduplication logic.

Quick Start

Integrate a new CGM data source by using the integrate-cgm-data-source skill. Provide the required details for the new glucose provider and configure the connection.

Frequently Asked Questions about integrate-cgm-data-source

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

FAQPage Schema

How do I integrate a new continuous glucose monitor data source into my application?▼

To integrate a new continuous glucose monitor data source, you need to automate database schema changes, create an API service class, and implement data synchronization. This process handles external glucose provider connections and credential storage for the T1D Companion.

What do I need to add support for CGM providers like Dexcom or Nightscout?▼

Adding support for CGM providers like Dexcom or Nightscout requires configuring database models for connection credentials and generating an API service class to interact with the external CGM APIs for data retrieval and synchronization.

Does Python automation handle database schema changes for new CGM data sources?▼

Yes, Python automation handles database schema changes by automatically adding new fields to the user database model to store CGM connection credentials and status when onboarding new continuous glucose monitor providers.

How do I sync continuous glucose monitor data and prevent duplicates?▼

You can sync continuous glucose monitor data and prevent duplicates by implementing data synchronization logic from external sources to the database. This includes built-in deduplication to ensure records remain unique during the sync process.

What knowledge is required to create an API service class for CGM data integration?▼

Creating an API service class for CGM data integration requires knowledge of CGM APIs, database schema design, and Python automation to properly configure the interaction between external glucose providers and the database.