Update to Gyroscope
Snapshot Nov 11, 2026 · 06:08 UTC · version 1.3.0
Collection source: downloaded plugin package.
Instructions updated for daily-recap
Skill instructions — Now says: `load_places` for the same dates, or `load_screen_time_day` for how the hours went on screen. ## Adding to their journal - When they want to note...
Observed in instructions or declared skills. Runtime behavior has not been tested.
Up to 3 plugins free · no card required.
All fields and original values.
Skill instructions
Oct 25, 2026 · 00:05 UTC
`load_places` for the same dates.
Nov 11, 2026 · 06:08 UTC
`load_places` for the same dates, or `load_screen_time_day` for how the hours went on screen. ## Adding to their journal - When they want to note something about their day for their Gyroscope coach, or track something Gyroscope has...
Compare saved observations
Download comparison JSONSKILL.md text changes
− removed · + added
--- before +++ after @@ -16,7 +16,8 @@ - `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. + `load_places` for the same dates, or `load_screen_time_day` for how the + hours went on screen. ## Writing the recap @@ -28,3 +29,12 @@ 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.
Full technical diff · 1 changed fields
changed /skill_md_contents
"---\nname: daily-recap\ndescription: Use when someone asks how their day or week went, what they did on a date, or for a summary of their Gyroscope data.\n---\n\n# A recap of a day or a week\n\nIf no Gyroscope tools are available, follow the connect-gyroscope skill\ninstead.\n\n## Getting the data\n\n- Call `gyroscope_status` once per conversation for the member's timezone and\n what this connection may access. Turn every relative date (\"yesterday\", \"last\n week\") into explicit YYYY-MM-DD dates in that timezone.\n- `load_day` covers up to 7 days per call: food totals, sleep, steps, workouts\n and places when allowed. For more detail on one topic, use `load_food`,\n `load_sleep`, `load_steps`, `load_workouts`, `load_computer` or\n `load_places` for the same dates.\n\n## Writing the recap\n\n- Lead with what matters most that day, then the rest in a few short lines.\n Use their numbers as the proof points.\n- Mention only what is there. A category with no data gets one plain line or\n is left out, with no guessing about why.\n- Write durations of an hour or more in decimal hours, and shorter ones in\n minutes.\n- If the result lists categories this connection cannot access, say once which\n ones, and that they can switch them on from their connection page.\n"
"---\nname: daily-recap\ndescription: Use when someone asks how their day or week went, what they did on a date, or for a summary of their Gyroscope data.\n---\n\n# A recap of a day or a week\n\nIf no Gyroscope tools are available, follow the connect-gyroscope skill\ninstead.\n\n## Getting the data\n\n- Call `gyroscope_status` once per conversation for the member's timezone and\n what this connection may access. Turn every relative date (\"yesterday\", \"last\n week\") into explicit YYYY-MM-DD dates in that timezone.\n- `load_day` covers up to 7 days per call: food totals, sleep, steps, workouts\n and places when allowed. For more detail on one topic, use `load_food`,\n `load_sleep`, `load_steps`, `load_workouts`, `load_computer` or\n `load_places` for the same dates, or `load_screen_time_day` for how the\n hours went on screen.\n\n## Writing the recap\n\n- Lead with what matters most that day, then the rest in a few short lines.\n Use their numbers as the proof points.\n- Mention only what is there. A category with no data gets one plain line or\n is left out, with no guessing about why.\n- Write durations of an hour or more in decimal hours, and shorter ones in\n minutes.\n- If the result lists categories this connection cannot access, say once which\n ones, and that they can switch them on from their connection page.\n\n## Adding to their journal\n\n- When they want to note something about their day for their Gyroscope coach,\n or track something Gyroscope has no tracker for, use `add_to_journal` in\n their words: \"Today is my anniversary!\", \"Today I wore jeans and black\n boots.\", \"Today I had 4 meetings at work.\" with the number 4.\n- One entry per thing, each with at most one number. If you wrote the entry up\n from what they told you, show it to them before adding it.\n"
Full snapshot data
{
"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.",
"included_files": [],
"name": "daily-recap",
"skill_md_contents": "---\nname: daily-recap\ndescription: Use when someone asks how their day or week went, what they did on a date, or for a summary of their Gyroscope data.\n---\n\n# A recap of a day or a week\n\nIf no Gyroscope tools are available, follow the connect-gyroscope skill\ninstead.\n\n## Getting the data\n\n- Call `gyroscope_status` once per conversation for the member's timezone and\n what this connection may access. Turn every relative date (\"yesterday\", \"last\n week\") into explicit YYYY-MM-DD dates in that timezone.\n- `load_day` covers up to 7 days per call: food totals, sleep, steps, workouts\n and places when allowed. For more detail on one topic, use `load_food`,\n `load_sleep`, `load_steps`, `load_workouts`, `load_computer` or\n `load_places` for the same dates, or `load_screen_time_day` for how the\n hours went on screen.\n\n## Writing the recap\n\n- Lead with what matters most that day, then the rest in a few short lines.\n Use their numbers as the proof points.\n- Mention only what is there. A category with no data gets one plain line or\n is left out, with no guessing about why.\n- Write durations of an hour or more in decimal hours, and shorter ones in\n minutes.\n- If the result lists categories this connection cannot access, say once which\n ones, and that they can switch them on from their connection page.\n\n## Adding to their journal\n\n- When they want to note something about their day for their Gyroscope coach,\n or track something Gyroscope has no tracker for, use `add_to_journal` in\n their words: \"Today is my anniversary!\", \"Today I wore jeans and black\n boots.\", \"Today I had 4 meetings at work.\" with the number 4.\n- One entry per thing, each with at most one number. If you wrote the entry up\n from what they told you, show it to them before adding it.\n"
}SHA-256 of public snapshot: b23afbe73ab0ff019a8cabb5efd67210a92e66fe62abfd3a4f19f7eccfb4fea5