Update to Gyroscope

{
  "description": "Use when someone asks about their sleep or sleep score in Gyroscope, how it has changed, or what lines up with it, such as workouts, steps, food, caffeine or travel.",
  "included_files": [],
  "name": "sleep-review",
  "skill_md_contents": "---\nname: sleep-review\ndescription: Use when someone asks about their sleep or sleep score in Gyroscope, how it has changed, or what lines up with it, such as workouts, steps, food, caffeine or travel.\n---\n\n# Reviewing sleep\n\nIf no Gyroscope tools are available, follow the connect-gyroscope skill\ninstead.\n\n## Getting the data\n\n- Call `gyroscope_status` once for the member's timezone, then use explicit\n  YYYY-MM-DD dates.\n- Specific nights: `load_sleep` for those dates. Each date is the night that\n  ended that morning, then any naps. When `confirmed` is false, the night is a\n  rough estimate from raw data, so say so.\n- Weeks or months: `load_trend` with metric `sleep`.\n- What lines up with it: the same nights with `load_workouts`, `load_steps`,\n  `load_food` or `load_computer`, `load_history` for caffeine, heart rate\n  and HRV, and\n  `load_places` when travel matters and Places is allowed. Look at two to four\n  weeks or more, in a few calls rather than one huge one.\n\n## Writing the answer\n\n- Give the sleep score and hours first, then what changed and when.\n- Write durations of an hour or more in decimal hours.\n- For patterns, compare the better and worse nights on the things that\n  differ, say how many nights each pattern rests on, and keep it plain when the\n  sample is small.\n- Point out patterns in their own data, and keep to what the numbers show.\n"
}