A weekly training review with Claude and Garmin, and Claude Code for power users

No coding needed for most of this post. If you're a developer who wants Garmin data in your own app, see Build with Garmin data instead.

Over the last three parts you've connected Garmin to Claude, learned to ask good questions, and had Claude build workouts for your watch. This last part is about making it part of your week:

The most useful habit I've found: every Monday morning, one message, and a short review of the week before.

To avoid typing the same long request every week, put it in a Claude Project. A project keeps instructions that apply to every chat inside it.

You are my training assistant. I'm a recreational runner training for a half marathon on 7 December. My easy pace is about 5:40/km. Use my Garmin data. When I say "weekly review", look at the last 7 days and give me: 1. Training: activities, total distance and time, compared with the previous week. 2. Recovery: average sleep, overnight HRV and resting heart rate, compared with my last 4 weeks. Flag anything unusual. 3. One thing that went well, and one thing to change next week. Keep it under 200 words, use a small table for the numbers, and say if any days have no data. Enter fullscreen mode Exit fullscreen mode Every Monday, open a new chat inside the project and type: weekly review. That's it. Edit the instructions as your goals change: a new race, a new focus, a week off.

A few additions that work well, once the basic review feels right:

The connector can also write some things to your Garmin account, which is handy for data your watch doesn't capture:

These show up in the Garmin Connect app like anything you'd entered there yourself.

This section is for people comfortable with a terminal. If that's not you, the review above is all you need.

Claude Code is Claude in your terminal. It can use the same Garmin connector, and because it works with files, it can save your reviews as Markdown files you keep: a training diary that writes itself.

claude mcp add --transport http garmin https://garmin.ficdev.xyz/mcp Enter fullscreen mode Exit fullscreen mode Then start Claude Code, type /mcp, choose garmin, and sign in to Garmin in the browser window that opens. ( claude mcp login garmin in the terminal does the same.) You only do this once.

Inside Claude Code, in a folder where you keep training notes:

Do my weekly training review from my Garmin data for the last 7 days and save it as reviews/2026-W43.md: activities, distance, sleep, HRV and resting heart rate compared with the previous 4 weeks, and one suggestion for next week. Enter fullscreen mode Exit fullscreen mode Claude fetches the data, writes the file, and shows you what it wrote. A few months in, you have a folder of weekly reviews you can search, compare and ask questions about: "Read my reviews from September and October. What changed?"

Claude Code can also run a single request without opening a chat, which means a scheduler can run it for you:

claude -p "Do my weekly training review from my Garmin data for the last 7 days and save it as reviews/ $( date +%G-W%V ).md" \ --allowedTools "mcp__garmin" "Write" Enter fullscreen mode Exit fullscreen mode -p runs one request and exits. --allowedTools gives it permission, ahead of time, to use the Garmin connector and to write files, since nobody is there to click "allow". Keep that list short: here it's only Garmin and writing files.

That command is for macOS and Linux terminals: $(date +%G-W%V) fills in this week's number, like 2026-W43, and the \ continues the line. In Windows PowerShell, write it on one line and let Claude name the file:

claude -p "Do my weekly training review from my Garmin data for the last 7 days and save it in the reviews folder, named after this week's ISO year and week number, like reviews/2026-W43.md" --allowedTools "mcp__garmin" "Write" Enter fullscreen mode Exit fullscreen mode Put that command in a weekly cron job (macOS and Linux) or Task Scheduler task (Windows), and the review appears in your folder every Monday before you wake up.

If Garmin has no data for the week, Claude may not save a file at all, and explains why instead. It did exactly that when I tested this on an account with no watch data. In a scheduled run nobody reads that explanation, so a missing file usually means your watch hasn't synced.

One honest caution: an automated run can't ask you anything. Keep scheduled requests to reading and reporting, and do anything that writes to Garmin, like scheduling workouts, interactively, where you can check the preview.

Everything so far used the hosted connector at garmin.ficdev.xyz. It's convenient, and it doesn't store your Garmin data or your password: your Garmin session lives encrypted inside the connection your Claude account keeps.

If you'd still rather nothing ran on someone else's server, there's a fully local option for Claude Desktop: the Garmin Desktop Extension.

Your Garmin session is then saved on your computer and talks to Garmin directly. The same questions, workouts and reviews work exactly as before. In the extension's settings you can also turn off tool groups you don't use, which keeps Claude focused.

Over four posts you've gone from connecting Garmin to Claude, to asking good questions, to letting it build and schedule workouts, to a weekly review that runs itself.

If this has become part of your training week, I'd love to hear how you use it. Share your weekly-review instructions in the comments; I'll collect the best ones.