Withings Family

**Judgement:** Solid, well-scoped Withings integration focused on read-only health data (weight, body composition, activity, sleep) with strong multi-user support. Good fit whenever an agent needs structured data from Withings devices for one or more family members. **Strengths & scenarios where it’s recommended:** - When the user explicitly mentions Withings devices (Body+, ScanWatch, Sleep Analyzer) or “Withings data.” - For checking recent weight, body fat %, muscle mass, or hydration trends from a smart scale. - For summarizing steps, distance, calories, or activity time over the last N days. - For reviewing sleep duration, sleep stages, and basic sleep quality over recent nights. - In multi-user or family contexts where each person has their own Withings account and should be addressed via a distinct userId. **Key risks / limitations:** - **Privacy & PHI:** The skill surfaces personal health data; agents must only query explicitly consented users and avoid mixing or exposing one family member’s metrics to another without clear user intent. - **Setup complexity:** Requires creating a Withings developer app, configuring environment variables, and completing OAuth per user, which may be non-trivial for less technical operators. - **External dependency:** Reliability and latency depend on the Withings API (e.g., 401/503 errors, empty data if devices are not syncing). The agent should interpret such errors and guide the user rather than assuming data is always available. - **Read-only and raw-data oriented:** Provides recent entries in JSON but does not perform advanced analytics, long-term trend detection, or alerting on its own; those need to be implemented at the agent or application layer.