Gyroscope

View saved version →

---
name: connect-gyroscope
description: Use when someone asks about their Gyroscope data or asks to log something, but no Gyroscope tools are available in this chat, or when they ask how to connect Gyroscope, what it can access, or why a category is missing.
---

# Connecting Gyroscope

Gyroscope works only with a connected Gyroscope account. Every answer about
their food, sleep, workouts, weight or places comes from the Gyroscope tools,
and every log goes through them. Without those tools there is no data to
answer from and nothing to log into.

## When the Gyroscope tools are not available

- Say plainly that Gyroscope is not connected in this chat yet, and help them
  connect it. Never answer from guesses, never invent numbers, and never say
  something was logged.
- Connecting starts from the Gyroscope plugin in ChatGPT. It opens a sign-in on
  gyrosco.pe, so ChatGPT never sees their password. They then choose what to
  share and approve it.
- Anyone without a Gyroscope account can create one at gyrosco.pe or in the
  Gyroscope app, then connect.
- Once connected, offer to pick up the request they started with.

## What a connection includes

- Included: food and nutrition, sleep, steps, workouts and lifts, fitness
  test and brain game results, weight, heart rate and HRV, screen time
  (computer and phone, the apps they use, pickups and notifications),
  weather, and account basics such as their timezone.
- Optional, each off unless they switch it on: places and travel history,
  their mood and their journal. These are more personal, so never load them
  without their explicit permission or request.
- Logging is on by default and can be switched off for a look-only connection.
  In ChatGPT it covers what they ate and what they did: meals, drinks,
  workouts, runs, rides and lifts, and journal notes. Nothing else goes in
  through this connection, it adds nothing they did not ask to log, and it
  cannot edit or delete anything.

## When a category is missing

- A tool that answers `insufficient_scope` includes a link to their connection
  page on gyrosco.pe. Give them that link. The change applies to their next
  question, with no need to reconnect. Do not retry until they say they have
  allowed it.
- `connection_revoked` means they disconnected. They can connect again from
  the Gyroscope plugin.
- If Gyroscope says something is not included in their account, pass that on
  plainly with the link it gives.

They can review, change or end what each assistant can access at any time at
gyrosco.pe/account/connections/.

View saved version →

---
name: daily-recap
description: Use when someone asks how their day or week went, what they did on a date, or for a summary of their Gyroscope data.
---

# A recap of a day or a week

If no Gyroscope tools are available, follow the connect-gyroscope skill
instead.

## Getting the data

- Call `gyroscope_status` once per conversation for the member's timezone and
  what this connection may access. Turn every relative date ("yesterday", "last
  week") into explicit YYYY-MM-DD dates in that timezone.
- `load_day` covers up to 7 days per call: food totals, sleep, steps, workouts
  and places when allowed. For more detail on one topic, use `load_food`,
  `load_sleep`, `load_steps`, `load_workouts`, `load_computer` or
  `load_places` for the same dates, or `load_screen_time_day` for how the
  hours went on screen.

## Writing the recap

- Lead with what matters most that day, then the rest in a few short lines.
  Use their numbers as the proof points.
- Mention only what is there. A category with no data gets one plain line or
  is left out, with no guessing about why.
- Write durations of an hour or more in decimal hours, and shorter ones in
  minutes.
- If the result lists categories this connection cannot access, say once which
  ones, and that they can switch them on from their connection page.

## Adding to their journal

- When they want to note something about their day for their Gyroscope coach,
  or track something Gyroscope has no tracker for, use `add_to_journal` in
  their words: "Today is my anniversary!", "Today I wore jeans and black
  boots.", "Today I had 4 meetings at work." with the number 4.
- One entry per thing, each with at most one number. If you wrote the entry up
  from what they told you, show it to them before adding it.

View saved version →

---
name: log-food
description: Use when someone tells you what they ate or drank, or asks to log a meal, snack, drink, coffee, alcohol, water or supplement in Gyroscope, including "the same as yesterday's breakfast".
---

# Logging food and drinks in Gyroscope

Everything logged goes into the member's own Gyroscope account, just as if
they had typed it in the app, so a wrong entry is a real cost to them. If no
Gyroscope tools are available, follow the connect-gyroscope skill instead.

## Before logging

- Anything consumed can be logged: meals, snacks, water and other drinks,
  coffee, alcohol, supplements, vitamins, powders and electrolytes.
- When the description is clear enough to estimate (a named dish with its main
  parts, a packaged item, a drink and its size), estimate and log it.
- Accuracy is the point. Portion size, cooking method and sides move the
  numbers a lot, so when a dish varies too much to estimate well and they gave
  no detail, ask one short question first. If they answer, or tell you to just
  log it, estimate from a typical portion and log it.
- Use the member's timezone from `gyroscope_status` for each time. "Just now"
  means now, and a named meal without a time means that meal today.

## Logging

- Call `save_food` with your estimate of all four: calories, protein, carbs and
  fat. Gyroscope keeps those and adds fiber, sugar and micronutrients itself.
  If you truly cannot estimate, send the caption alone and Gyroscope analyzes
  it.
- The caption is what they consumed, in plain words, never the numbers.
- Leave `meal` out unless they named one. Gyroscope files the entry by their
  meal schedule.
- Several items eaten together are logged together, one item each.
- For a repeat of an earlier meal, find it with `load_food` on that day, then
  use `log_again` with the item id, which keeps any photo.

## After logging

- Confirm in one line: what was logged, when, and the estimate you used.
- A retry with the same details lands on the same entry, so a repeated call
  never doubles a meal.
- The connection cannot edit or delete entries. If they want a fix or a
  removal, say it is done in the Gyroscope app.

View saved version →

---
name: nutrition-review
description: Use when someone asks about their eating patterns, calories, protein or macros over time in Gyroscope, how their eating relates to their weight, or wants meals planned around their own targets and the foods they already eat.
---

# Reviewing nutrition and planning meals

If no Gyroscope tools are available, follow the connect-gyroscope skill
instead. To log something they ate, use the log-food skill.

## Getting the data

- Call `gyroscope_status` once for the member's timezone, then use explicit
  YYYY-MM-DD dates.
- What they ate: `load_food` for the dates in question, up to a few weeks in a
  few calls.
- Totals over time: `load_trend` with metric `calories` or `protein`, weekly
  or monthly.
- Sodium, potassium, saturated fat, cholesterol, calcium, iron and
  magnesium come with every item and day from `load_food` and `load_day`.
  For another nutrient (a vitamin, zinc), pass `nutrients` with its name
  and unit (`vitamin_d_mcg`) to `load_food`, or to `load_history` with
  kind `food` for a month at a time. A null or empty cell means
  Gyroscope's analysis of that item did not cover it; say how many items
  a day's total rests on.
- Their targets: use the calorie and protein targets they give you. If they
  have not said them, ask once.

## Patterns

- Name the meals and foods that come up most, when they tend to eat, and how
  calories and protein compare with their targets.
- When they are working on their weight, line up weekly calories with weekly
  weight (`load_trend` with metric `weight`, or `load_history` with kind
  `weight` for the weigh-ins)
  and say how the two moved together.
- Say how many days each pattern rests on.

## Meal plans

- Build from their real targets and the meals they already eat, adjusting
  portions and swaps rather than starting from nothing.
- Give rough calories and protein per meal so the plan can be checked against
  the target.
- Plans are suggestions. Log a meal only when they say they ate it.

View saved version →

---
name: reports
description: Use when someone asks for a chart, graph, spreadsheet, report, summary page, infographic or export of their Gyroscope history, or wants their data in a file or a custom format.
---

# Charts, spreadsheets, reports and infographics from Gyroscope history

The Gyroscope tools provide the data. ChatGPT makes the chart, the file or
the page from it. If no Gyroscope tools are available, follow the
connect-gyroscope skill instead.

## 1. Agree the shape

- Settle three things before loading anything: the date range, the kinds
  of data (sleep, meals, workouts, lifts, steps, weight, heart rate, screen
  time, places), and the output (a chart, a spreadsheet, a one-page report, an
  infographic, a CSV). Default to the last 30 days and one page when they
  have not said.
- Call `gyroscope_status` once for the member's timezone, then use explicit
  YYYY-MM-DD dates.

## 2. Load the data

- Weekly or monthly numbers for a chart or a summary: `load_trend` with one
  metric (steps, sleep, calories, protein, weight, workouts, rhr, hrv) over
  up to a year. One call per metric.
- Rows for a spreadsheet or a detailed chart: `load_history` with one kind
  or a bundle (fitness, nutrition, sleep_all, places) for one month, or a
  start and end date. Walk a longer span month by month, and keep calling
  with `page = next_page` while `has_more` is true. The rows come as CSV
  text under a `columns` header.
- A short period in full: `load_day` (7 days per call) or the single-topic
  reads for the same dates.
- Screen time by day, week or month with the top apps: `load_screen_time`
  over up to a year. One app over time: `load_app_usage` with `app`.
- Lifts by exercise over time: `load_lift_progress`, with `exercise` for one
  line per session.
- Places need the Places permission. On `insufficient_scope`, give them the
  link and leave places out until they allow it.
- Load what the output needs and no more. A one-page review of a month does
  not need a year of heart rate samples.

## 3. Build the output in ChatGPT

- Chart or infographic: use ChatGPT's own data analysis and image tools on
  the loaded rows. One chart per question, labelled axes, the unit in the
  label, the date range in the title.
- Spreadsheet or CSV: write the rows as loaded, one sheet or file per kind,
  with the `columns` header as the first row and the member's local times
  as given.
- Report or summary page: lead with the two or three numbers that changed
  most, then one short section per kind, each resting on the loaded data.
  Say how many days each figure covers.
- Durations of an hour or more in decimal hours, shorter ones in minutes.
  Weight in the units the member uses.
- Every number in the output comes from a tool answer. Never fill a gap with
  an estimate. Say which days have no data instead.

## 4. Hand it over

- Give the file or image, name the date range and the kinds it covers, and
  offer one follow-up, such as the same report for the month before.

View saved version →

---
name: screen-time
description: Use when someone asks about their screen time, phone or computer use, which apps take their time, phone pickups or notifications, or how focused or productive their days were, in Gyroscope.
---

# Screen time, apps and pickups

If no Gyroscope tools are available, follow the connect-gyroscope skill
instead.

## Getting the data

- Call `gyroscope_status` once for the member's timezone, then use explicit
  YYYY-MM-DD dates.
- Start with `load_screen_time` for the range they asked about, by day, week
  or month: computer and phone time, productive and unproductive time,
  pickups, notifications, first and last pickup, and the top apps per device.
- For the hours of a day ("when was I on my phone last night?"):
  `load_screen_time_day`, up to 7 dates.
- For one app or website over time: `load_app_usage` with `app` (part of the
  name is enough). Without `app` it ranks their apps by time.
- Load the totals first and only drill into days or apps the question needs.

## Reading it right

- Phone time comes from Screen Time imports in the Gyroscope app, so some days
  have none. Say how many days the phone numbers rest on (`phone_days`), and
  compare averages over those days, not raw totals across weeks with
  different coverage.
- Productive and unproductive come from each app's category in Gyroscope.
  Present them as that, not as a judgement of their day.
- Line screen time up with sleep, steps or places when they ask what changed,
  using their numbers as the proof points.
- Write durations of an hour or more in decimal hours, and shorter ones in
  minutes.

View saved version →

---
name: setup
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.
---

# Setting up Gyroscope

This runs once, right after the member adds Gyroscope. Keep it short and
friendly, and log nothing during setup.

## 1. Check the connection

- Call `gyroscope_status`.
- If no Gyroscope tools are available, or the connection is missing, follow the
  connect-gyroscope skill to get them connected, then continue here.

## 2. Confirm what is shared

- In two or three lines, confirm the connection works, the timezone Gyroscope
  will use for their dates, and the categories this connection can access.
- Name the optional categories that are off (places and travel, their mood
  and their journal), and say they can switch each one on at
  any time at
  gyrosco.pe/account/connections/.
- If logging is off, say that this connection can look things up but not add
  entries, and how to switch it on there.

## 3. Show it working

- Make one call to `load_day` for yesterday and give a one-line snapshot from
  whatever is there, such as what they ate, how they slept and their steps.
- If yesterday is empty, say so in one line and move on.

## 4. What to try next

- Offer three short ideas in their own context, one of each kind: logging what
  they eat or drink by just telling you, lining up two things from their
  wearables such as sleep against workouts, and a recap of the places they
  went or a trip they took.
- Then hand the conversation back to them.

View saved version →

---
name: sleep-review
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.
---

# Reviewing sleep

If no Gyroscope tools are available, follow the connect-gyroscope skill
instead.

## Getting the data

- Call `gyroscope_status` once for the member's timezone, then use explicit
  YYYY-MM-DD dates.
- Specific nights: `load_sleep` for those dates. Each date is the night that
  ended that morning, then any naps. When `confirmed` is false, the night is a
  rough estimate from raw data, so say so.
- Weeks or months: `load_trend` with metric `sleep`.
- What lines up with it: the same nights with `load_workouts`, `load_steps`,
  `load_food` or `load_computer`, `load_history` for caffeine, heart rate
  and HRV, and
  `load_places` when travel matters and Places is allowed. Look at two to four
  weeks or more, in a few calls rather than one huge one.

## Writing the answer

- Give the sleep score and hours first, then what changed and when.
- Write durations of an hour or more in decimal hours.
- For patterns, compare the better and worse nights on the things that
  differ, say how many nights each pattern rests on, and keep it plain when the
  sample is small.
- Point out patterns in their own data, and keep to what the numbers show.

View saved version →

---
name: training-review
description: Use when someone asks about their workouts, runs, rides, steps, strength progress or fitness test results in Gyroscope, or wants to log a workout that no device tracked.
---

# Reviewing and logging training

If no Gyroscope tools are available, follow the connect-gyroscope skill
instead.

## Reviewing

- Call `gyroscope_status` once for the member's timezone, then use explicit
  YYYY-MM-DD dates.
- Sessions: `load_workouts` for the dates. Steps: `load_steps`.
- Lifts over time: start with `load_lift_progress`, which lists each
  exercise with its sessions and best, first and latest estimated one-rep
  max. Name an exercise ("bench") for one line per session: the top set,
  the estimated max and the volume. Use `load_strength_history` only when
  they want every set.
- Fitness tests and brain games from the app: `load_benchmarks` gives each
  test's latest, previous and best result with its score out of 100, and the
  tests they have not taken yet. Name a test for every run of it.
- Totals over weeks or months: `load_trend` with metric `workouts` or `steps`.
- Their current program: `load_workout_state`, which you can see but not
  change.
- Lead with the change that matters (heavier, longer, more often), backed by
  their numbers, and line it up with their sleep or weight when they ask.

## Logging a workout

- Manual sessions (`save_workout`, `save_run`, `save_bike`) are only for what
  no device tracked. Check `load_workouts` for that day first, and never save
  over a session that is already there.
- Ask for the one missing detail, such as duration or start time, rather than
  guessing it.
- Lifts go on an existing workout with `add_strength_training_details`, using
  its id from `load_workouts`. Show them the sets you are about to log first.
- Confirm in one line what was logged and when. The connection cannot edit or
  delete anything, so changes are done in the Gyroscope app.

View saved version →

---
name: travel-recap
description: Use when someone asks where they went, about a trip, the places, restaurants or cities they visit most, their jetlag, or how travel changed their sleep, eating or routine in Gyroscope.
---

# Places and travel

If no Gyroscope tools are available, follow the connect-gyroscope skill
instead.

## Getting the data

- Places is optional and off unless the member switched it on. If
  `load_places` answers `insufficient_scope`, give them the link it includes
  and say it applies to their next question. Do not retry until they say they
  have allowed it.
- Call `gyroscope_status` once for the member's timezone, then use explicit
  YYYY-MM-DD dates.
- `load_places` returns visits with the place, its category, the city, arrival
  and departure, up to 7 days per call. For a long span, use `load_history`
  with kind `gvisits` (visits) or `travels` (trips, distance and mode) by
  month.
- `load_weather` gives the weather where they were on a date, for a trip
  recap or a "what was it like" question.

## Writing the answer

- For a trip, give the cities and the main places in order, with how long they
  stayed, and the distance when they ask how far they went.
- For favorites, count visits and name the places, restaurants, cafes and
  cities that come up most.
- For how travel changed their routine, line up the trip's dates with
  `load_sleep`, `load_food` or `load_steps` and compare them with the weeks
  at home.
- For jetlag, work out the time zones crossed and the direction from the
  arrival and departure times, then suggest how to plan the next few days.
- Location history is sensitive. Share only what answers their question.