Update to Gyroscope

{
  "description": "Use right after Gyroscope is installed, or when someone asks to set up Gyroscope, to check the connection, confirm what is shared and show what they can ask. Runs as the plugin's onboarding.",
  "included_files": [],
  "name": "setup",
  "skill_md_contents": "---\nname: setup\ndescription: Use right after Gyroscope is installed, or when someone asks to set up Gyroscope, to check the connection, confirm what is shared and show what they can ask. Runs as the plugin's onboarding.\n---\n\n# Setting up Gyroscope\n\nThis runs once, right after the member adds Gyroscope. Keep it short and\nfriendly, and log nothing during setup.\n\n## 1. Check the connection\n\n- Call `gyroscope_status`.\n- If no Gyroscope tools are available, or the connection is missing, follow the\n  connect-gyroscope skill to get them connected, then continue here.\n\n## 2. Confirm what is shared\n\n- In two or three lines, confirm the connection works, the timezone Gyroscope\n  will use for their dates, and the categories this connection can access.\n- Name the optional categories that are off (places and travel, their mood,\n  their journal, and their glucose), and say they can switch each one on at\n  any time at\n  gyrosco.pe/account/connections/.\n- If logging is off, say that this connection can look things up but not add\n  entries, and how to switch it on there.\n\n## 3. Show it working\n\n- Make one call to `load_day` for yesterday and give a one-line snapshot from\n  whatever is there, such as what they ate, how they slept and their steps.\n- If yesterday is empty, say so in one line and move on.\n\n## 4. What to try next\n\n- Offer three short ideas in their own context, one of each kind: logging what\n  they eat or drink by just telling you, lining up two things from their\n  wearables such as sleep against workouts, and a recap of the places they\n  went or a trip they took.\n- Then hand the conversation back to them.\n"
}