health-setuplisted

# health-setup, interactive wearable connector wizard Walks the user from "I have an Apple Watch / Oura / Fitbit" to "data is in my DuckDB and I can run /weekly with body track populated." The wizard branches by: 1. Which wearable(s) they have 2. Which OS they're on (macOS / Windows / Linux) 3. Whether they're starting fresh or adding a second device It never installs anything they don't want. Each branch has its own setup path — most of them are 3-5 manual steps and a paste-into-shell to set env vars. ## When to use - User says `/health-setup` or `/setup-health` or `setup my health connector` - User asks "how do I import Oura / Fitbit / my Apple Watch data" - User says "which wearable should I use" — pick + walk through setup - After a fresh install of the ai-brain-starter substrate - After health-mcp v0.3+ is registered but no data is imported yet Do NOT use for: - Querying already-imported data (use `health_status`, `health_recovery_score`, etc.) - Building new wearable connectors (that's a substrate dev task) - Onboarding non-health skills ## Wizard flow ### Step 1: Detect the OS Look for `darwin` / `linux` / a Windows path separator in the environment. Confirm with the user if uncertain. Map to one of: `macos`, `linux`, `windows`. ### Step 2: Ask which wearable(s) they have Multiple-select. The substrate currently supports first-class: - **Apple Watch / iPhone (Apple Health)** — most common, free, works without iPhone-paired apps - **Oura Ring** — free Person