health-doctor

Monitor health data freshness across Apple Health, Oura, Fitbit, and labs.

31|20|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/mycelium-hq/ai-brain-starter --skill health-doctor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: health-doctor
Source: https://github.com/mycelium-hq/ai-brain-starter/tree/main/skills/health-doctor
Command: npx skills add https://github.com/mycelium-hq/ai-brain-starter --skill health-doctor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The health-doctor surface provides a concise observability layer for health data pipelines, showing data freshness, coach prescriptions, missed days, lab status flags, and which auto-trigger hooks are installed to catch silent failures.

Core Features & Use Cases

  • Data freshness across Apple Health, Oura, Fitbit, and labs, with time-since-last-import metrics.
  • Prescription visibility for the latest coach guidance and whether it was completed, including streaks and missed days.
  • Auto-trigger awareness by verifying that startup and stop hooks are registered and firing as configured.
  • Profile and lab context by surfacing coach-profile state and lab-status flags to guide remediation or re-testing.
  • Debugging workflows for onboarding or diagnosing sync and calendar issues.

Quick Start

Run /health doctor to generate a live observability report and verify all health data sources and auto-trigger hooks are functioning.

Frequently Asked Questions about health-doctor

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

FAQPage Schema
How do I monitor health data freshness across Apple Health, Oura, and Fitbit?

To monitor health data freshness, generate a live observability report that checks time-since-last-import metrics across Apple Health, Oura, Fitbit, and labs. This surfaces sync issues and verifies data pipelines are actively importing.

What is health data observability and why do I need it for wearable pipelines?

Health data observability provides a concise layer showing data freshness, missed days, and lab status flags for wearable pipelines. It helps diagnose silent sync failures and ensures coaching prescriptions rely on current data.

How do I verify auto-trigger hooks are firing for health data ingestion?

You can verify auto-trigger hooks are firing by checking the observability report, which confirms that startup and stop hooks are registered and functioning as configured to catch silent failures during data ingestion.

Can I check if my health coach prescriptions were completed and track missed days?

Yes, you can check prescription visibility to see the latest coach guidance, completion status, and streaks. The observability surface tracks missed days to help maintain adherence to health coaching prescriptions.

How do I debug sync issues and calendar updates for health data pipelines?

To debug sync issues and calendar updates, run the observability report to surface data freshness metrics, coach-profile state, and lab-status flags. This diagnostic workflow guides remediation for onboarding or sync failures.

Does this health data monitoring work without external dependencies?

Yes, this health data monitoring operates without external dependencies. It integrates with vault and config files to compile comprehensive observability reports using existing health status and coach prescription functions.