Skip to content
TriedPrompts

More in Hobbies, Fitness & Learning.

Turn Claude into a blunt running coach with Garmin data and markdown files

Copy the prompt below and paste it into the AI tool named on this page.

Prompt Recreated prompt

The source didn't share its exact prompt, so we wrote this from what it describes.

What the prompt labels mean

You are my running coach. Pull each run from my Garmin through the connector, look at the per-lap splits and heart rate zones, not just the averages, write a report for each session and update my analysis file. Be blunt and don't play along when I try to convince myself a mediocre session was good.

Try this in:

Sends the Recreated prompt shown above. ChatGPT and Grok open with it filled in, and ChatGPT may send it straight away. Gemini opens empty, so we copy the prompt for you to paste. Every button also copies it.

The source used Claude. These are general chat tools, so results may differ.

Opens in a new tab. We don't see what you send.

These links are only a shortcut. We're not affiliated with OpenAI, Google or xAI, and your results may not match the source.

Optional stronger version

Our rewrite with extra checks. The poster didn't test it.

Before you start, ask me 1–3 short questions about the details below and wait for my answers. Once I've answered, confirm the plan in one line and run the whole task start to finish.

Goal: Coach my running from my real watch data, with honest feedback and a plan that changes when the data says it should.

Questions to ask me first:
- What's your goal (race, distance or fitness), and by when?
- What are your heart rate zones, and where did they come from?
- How many days a week can you run, and any injuries?

Inputs (fill in or confirm):
- Watch data access (connector or export): [GARMIN / OTHER]
- Profile: zones, goal and known habits: [PROFILE]
- Weekly schedule: [SCHEDULE]
- Injuries or health limits: [LIMITS]

Rules:
- Analyze each run per lap, not by averages, and point out heart rate drift.
- Be blunt: if a session missed its target, say so and why.
- Keep a per-run report and one living analysis file so you remember past sessions.
- Change the plan when a workout type keeps failing, and write down the reason.

Checkpoint: After the first run, show me the report format and wait for my OK before using it for every session.

If you get stuck: If data is missing or looks wrong (bad heart rate readings), say so instead of drawing conclusions.

Verify before you finish: Check each report against the plan's target for that session.

Output: A per-run report, an updated analysis file and next week's plan.

Done when: Each run gets an honest report, and the plan adapts to what my data shows.

AI tool

Claude

Outcome

Sander Sneekes's running had stalled: VO2max moved only from 44 to 45 in nine weeks, and the 10K time sat around 63 minutes for months. Sneekes connected Claude to Garmin data through an MCP connector and set up a project folder with three markdown files: coach instructions, a runner profile and a living analysis, plus one report per run. The rules told Claude to look at per-lap data and not to play along when Sneekes tried to call a mediocre run good. In the first week, an 'easy' run averaging 130 bpm, under the 135 target, turned out per lap to drift from 119 to 146, with nearly a third in Zone 3. A failed interval session led the coach to rewrite hard workouts into longer blocks or tempo runs on cool days, and it caught a too-fast cooldown, adding the rule 'cooldown means walking.'

Evidence: Described by posterThe person describes what happened in words, without screenshots or video.

Source

Posted
by Sander Sneekes (personal blog)
Last checked
Method:
How we verify

https://sneekes.app/posts/claude-running-coach-garmin-mcp/

Context: Sneekes is technical and set up the Garmin MCP connector and file structure. The post covers one week of coaching, so longer-term results aren't known yet.

More in Hobbies, Fitness & Learning