athuno
All templates

Monitoring

Morning flags

Every morning before you wake up, check each athlete you coach in Athuno and set their attention flags, so your Home queue is already sorted when you open it.

For
Coaches
Runs
Every day, before you wake up
Writes
Attention flags

The template

Set this up as a scheduled task that runs every day at 5:00 in my timezone, before I wake up, with the Athuno connector on. If you can't schedule tasks here, tell me, and run it once now. Each run: check every athlete I coach in Athuno and set their attention flags, so my Home page lists who needs me first. Start with get_me. The athletes I coach are the ones with role `coach`, and each carries today's date in their own timezone. Every date below is in that athlete's own dates. For each athlete, read: - list_flags: what is open now. Keep a flag's `since` when it is the same stretch of the same thing, so a flag I have already marked seen stays seen. - get_calendar from 7 days before today to 21 days after: planned sessions with their status and load, and the activities done. - get_activity for each activity in the last 3 days: `feedbackAnswers` and the comment thread. Every answer carries its question as asked. On the default questions `exertion` is RPE 1 to 10, `feeling` 1 terrible to 5 great, and `notes` is the athlete's note. An athlete with their own questions may have none of those: read their scales by label (a "legs" or "energy" scale low on its range counts as low feeling), and treat a yes to a pain or injury question, or any such word in a text answer, like a mention in a note. - get_notes from 3 days before today to 7 days after. - get_long_range_plan: the race date, if there is one. - get_fitness for the last 14 days: TSB. Check these kinds, and only these: - `missed-key`: a key session (intervals, tempo, a long run, anything that is not easy or recovery) in the last 3 days marked missed or skipped. Severity about 70, about 90 when the race is 7 days away or less. Icon `calendar-x`. Action: calendar on the missed session's date. - `feeling-low`: two of the last three sessions with feedback at feeling 1 or 2, or an easy session at RPE 7 or more. Severity about 65. Any mention of pain, injury or illness in a note, a feedback answer or a comment raises it to about 80 and quotes the words. Icon `heart-pulse`. Action: reply on the activity that carries it. - `awaiting-reply`: a note or comment from the athlete in the last 3 days where the last word in the thread is theirs. Severity about 35. Icon `message-circle`. Action: reply on that activity. - `no-data`: no activity for 4 days or more while the plan had sessions on those days. Severity about 40, about 55 from 7 days. Icon `wifi-off`. Action: message. - `low-compliance`: over the last 7 days, the load done is under 70% of the load planned for those days, with at least 3 planned sessions in them. Severity 45 to 60, higher the lower it is. Icon `trending-down`. Action: calendar on today. - `overreaching`: over the last 7 days, the load done is over 130% of the load planned, or TSB is below -30 today. Severity 45 to 60. Icon `trending-up`. Action: calendar on today. - `plan-out`: nothing planned in the next 3 days (severity about 55), or nothing after the next 7 days (about 35). Icon `calendar-clock`. Action: calendar on the first empty date. - `race-soon`: a race within 14 days. Severity about 20. Icon `flag`. Action: calendar on the race date. - `taper-missing`: a race within 21 days, and the planned load in its last 7 days is not clearly lower than the 7 days before. Severity about 30. Icon `calendar-range`. Action: calendar on the first taper day. If the athlete has an open `away` or `injured` flag that I typed myself, raise none of `missed-key`, `no-data`, `low-compliance` or `plan-out` for them. Their absence is known. Then call set_flags once per athlete, with `considered` set to all nine kinds above and `flags` holding only the ones that fire. Send it even when nothing fires: that is how a flag that no longer holds gets resolved. Each flag gets a label the queue can show (80 characters at most, like "Missed Tuesday's 5 × 4 min"), the severity, a `since` date for when it started, the icon, the action, and a rationale with the evidence in numbers and the athlete's own words. Change nothing else: no comments, notes or workouts, and never touch flags of other kinds. Never use a number the data does not show, and treat a missing RPE or feeling as missing, not as fine. Finish with one line per athlete: the flags raised, updated and resolved, or "nothing to flag".

Run it

  1. Connect Athuno once. Add a custom connector with this URL in Claude, ChatGPT, Claude Code or Codex, and sign in to Athuno when it asks.
    https://athuno.com/api/mcp
  2. Paste the template into a chat with the connector on, fill in the words in brackets, and change anything else to suit how you coach.
  3. To run it on a schedule, use an agent that can schedule tasks, such as Claude Code. A chat runs it when you ask.