Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Triathlon Assessment & Weekly Plan from Your Garmin Data

    1

    If you ask, and your Garmin connection can write workouts, it turns sessions into structured Garmin workouts and schedules them after you confirm.

    $7

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Triathlon Assessment & Weekly Plan from Your Garmin Data

    Triathlon Assessment & Weekly Plan from Your Garmin Data

    Example session with this skill installed

    I'm building toward my first sprint triathlon next season. Look at my last 4 weeks of Garmin data and tell me where I stand and what to do this week.

    • Read your context and instructions
    • Compiled the triathlon assessment

    🏊‍♂️🚴‍♂️🏃‍♂️ Triathlon Training Assessment

    Window: 2026-09-23 to 2026-10-21 (last 4 weeks). Target: sprint triathlon (750 m / 20 km / 5 km), date not set yet.

    Current Fitness Snapshot

    MetricValueDate / note
    VO2 max54.0 (running)last changed 2026-07-08, no change in the last 90 days (no outdoor runs since); training status had none
    Training statusMaintaining2026-10-20 (today's status not synced yet)
    Acute / chronic load490 / 555 (Garmin ratio 0.8, "optimal")2026-10-20
    Monthly load by typeaerobic low 498 · aerobic high 727 · anaerobic 9072026-10-20. Garmin's verdict: aerobic low shortage
    Race predictions (running only)5K 22:32 · 10K 49:34 · half 1:54:04 · marathon 4:19:512026-10-21
    Endurance scorenot availablethe call returned an error
    Fitness agenot availableempty for 2026-10-21 and 2026-10-20

    Garmin bases its run predictions on VO2 max and recent training. You ran once in 4 weeks and the VO2 max behind them dates from July, so treat the 22:32 5K as what your engine could do, not what your legs can do right now off the bike.

    Discipline Balance (Last 4 Weeks)

    DisciplineSessionsDistanceTime% of timeAvg HRSprint benchmark
    Swim000 h0% ⚠️ critically undertrainedn/a20-25%
    Bike17375.9 km18.5 h71.8%142 (13 rides; 4 had no HR)40-45%
    Run15.25 km0.5 h1.9% ⚠️ critically undertrained16725-30%
    Strength5n/a6.8 h26.3%985-10%
    Total2325.8 h

    Weekly hours: 6.8 → 6.6 → 8.4 → 4.0 (weeks starting 09-23, 09-30, 10-07 and 10-14).

    Strength time is the time each session was recorded, rests included. One session ran 2 h 54 min. That inflates its share. Lifting 5 times in 4 weeks is a good habit to keep. The real problem is the other end of the table: swim and run together got under 2% of your time.

    Intensity Check

    DisciplineHR-zone dataZone 1-2Zone 3Zone 4-5Verdict
    Bike13 of 17 rides (16.9 h)64.0% (target ≥75%)23.3% (target ≤10%)12.7% (target ≤15%)Improving but needs more easy work
    Run1 of 1 (28 min)10.2%27.0%62.7%🚩 Intensity overload, running too hot
    Swimno swimsn/an/an/anot scored

    Bike: the leak is Zone 3, not all-out efforts. Only 5 of 13 rides with HR reached 75% in Zones 1-2, and one of those was a 3-minute ride. Your planned Zone 2 ride on 10-12 averaged 147 bpm and still spent 35% of its time in Zone 3. (The 10-04 ride was also planned as Zone 2 but turned into a sprint, so it doesn't count as drift.) Garmin's "aerobic low shortage" flag says the same thing from the load side.

    Run: the one treadmill run (5.25 km, average HR 167, max 190) spent 63% of its time in Zones 4-5. Garmin labelled it "Tempo". That was a hard session, not base running.

    Zone boundaries used: your bike zones are custom: Zone 2 is 136-149, Zone 3 is 150-169, Zone 4 is 170-187 and Zone 5 is 188+. Your run zones work out to exactly 50/60/70/80/90% of a 210 bpm max, which is higher than any heart rate in your data (the highest is 197). Your run zones look too high, so I'm not relying on them for the cap. Your custom bike zones put the top of Zone 2 at 149, and 146 sits just under that, so use

    146 bpm as a conservative easy-run cap for now. Then correct your running max HR or your run zones in Garmin, so the watch's run zones no longer rest on a 210 max. (Lower, correct run zones would only put more of the treadmill run in Zones 4-5, so its verdict stands.)

    Your Limiter

    DisciplineVolumeConsistencyIntensityPerceived difficultyScore
    Swim0 (0 h/wk vs 1.0 h)0 (0 per week)not scored (no HR data)not scored0
    Run8 (0.12 h/wk vs 1.5 h)8 (0.25 per week)25not scored14
    Bike100 (4.6 h/wk vs 2.0 h)100 (4.25 per week)60not scored87

    Sprint benchmarks. Perceived difficulty is unscored because I don't have your rating. Tell me how hard each discipline feels from 0 (very hard) to 100 (comfortable) and I'll add it.

    Your limiter is swimming, with running close behind. You haven't swum in 43 days. The last swim was 1,509 m on 2026-09-08. From late May to early September you logged 25 pool swims: a median of 800 m, 14 of them at 750 m or more, and the longest 2,850 m. So you already have the skill. You need to get back in the water.

    What to do: swim twice this week once you're out of the red, then build to 3 swims a week. The first goal is 750 m of continuous easy swimming. Running comes next. Before 10-08 your last runs were in early July, and they were all under 1.8 km. Bring running back short, easy and often, not as one hard treadmill session.

    Recovery Status: 🔴

    SignalValueDate / contextLight
    Training readiness27 (Low)2026-10-21, real-time update before today's sleep and HRV were in🔴
    Training readiness1 (Poor, "time to slow down")2026-10-20, after waking🔴
    Body battery at wake952026-10-20, end of sleep🟢
    HRV statusUnbalanced. 7-day average 47 ms vs a balanced range of 48-67 (last night 49)2026-10-20🟡
    Sleep5 h 14 min (score 77, "fair")night ending 2026-10-20🟡
    Resting HR52 (7-day average 53)2026-10-20n/a
    Stressaverage 272026-10-20n/a

    Training readiness decides the light: red. The other signals are mixed. Body battery refilled, but HRV is just below your range and sleep was short. Garmin's recovery timer showed 64 h after waking on 10-20 and 53.7 h at the latest update. This follows Monday's ride on 10-19: 81 min, average HR 159, max 197, 29% in Zones 4-5, training load 319. Today's sleep, HRV, body battery, stress and resting HR had not synced yet, so the values above are from 10-20.

    This Week's Plan

    Rule for the week: rest comes first. Do no training until your morning readiness is

    40 or higher, which is out of the red. If it is still below 40, that day becomes a rest day.

    Focus for this week
    1.

    Rest Wednesday and Thursday, and sleep more than 7 h. Easy walking is fine. Check readiness each morning after you wake up. Your last recorded night was 5 h 14 min, and a green light needs more than 7 h.
    2.

    Swim twice (30-35 min), drills first. Use catch-up and fingertip drag. Swimming is the limiter, and all of it should be easy.
    3.

    Run once, 20 min, as run-walk with HR under 146. Walk whenever you go over 146. This replaces the hard treadmill run.
    4. Keep both rides fully in Zone 2. HR stays under 150 the whole time. Your bike Zone 3 starts at 150. Soft-pedal the rises.
    5.

    Strength: one short session (20 min) this week, then go back to your normal routine once you're green (readiness above 60). Your normal sessions run long (one was 2 h 54 min), and until then recovery and the limiter sessions come first.

    DaySessionType
    Wed 10-21RestRecovery
    Thu 10-22Rest (easy walk OK)Recovery
    Fri 10-23Swim 30 min, about 1,000 m: 200 easy · 6×50 drill (catch-up / fingertip drag), 20 s rest · 4×100 relaxed, 30 s rest · 100 easy. Only if readiness ≥40Key (limiter), easy effort
    Sat 10-24Ride 60 min, Zone 2, HR under 150 the whole ride. Only if readiness ≥40Easy
    Sun 10-25Run-walk 20 min (4 min run / 1 min walk, ×4), HR cap 146 + strength 20 min (core, hips, calves). Only if readiness ≥40Key (limiter), easy effort
    Mon 10-26Swim 35 min, about 1,200 m: 200 easy · 6×50 drill · 3×200 easy, each one without stopping, 30 s rest · 100 easy. Only if readiness ≥40Key (limiter), easy effort
    Tue 10-27Ride 45 min, Zone 2 (HR under 150). Only if readiness ≥40Easy

    The days are placeholders until you tell me your week and when you can get to a pool. If you do everything, that's about 3.5 h, below last week's 4.0 h. That is deliberate while you recover. Swim takes about 31% of the time and bike about 50%. That is already much closer to a triathlete's split.

    Technique cues

    Swim: there were no swims in the window, so there is no stroke data to work from yet. Spend the drill sets on catch-up (one hand waits in front until the other arrives) and fingertip drag (high elbow on the recovery). Breathe every 3 strokes on the easy repeats to keep the stroke even on both sides.

    Bike: HR discipline is the cue. Your planned Zone 2 ride on 10-12 averaged 147 bpm, near the top of Zone 2, and still drifted into Zone 3 for 35% of the ride. Set an HR alert at 149 on the head unit. Cadence wasn't in the ride data I pulled, so I can't check it. Aim for 85-95 rpm on easy rides.

    Run: your watch's average cadence was

    145 spm, with an average stride of

    1.30 m. Steps ÷ time gives

    152 spm over the whole run, or

    167 spm over moving time. All three are below the 170-185 target. Take shorter, quicker steps (at the same speed, a shorter stride means a higher cadence), and keep the HR cap even if it means walking.

    Brick workouts

    Not yet. With no race date set, bricks aren't on the calendar. They start about 12 weeks before race day: short ones first (30 min bike → 10 min run), then weekly in the build phase, and at race pace in the peak.

    Race Readiness (Baseline)

    SubscoreScoreBand and reason
    Swim180-24. Capped there because there were 0 swims in the window. Moved up from the midpoint of 12 for your summer history (25 swims, the longest 2,850 m). History can't lift the band.
    Bike8570-89. You can ride the distance, but "at target pace" can't be tested. Moved up from 80 because 10 rides were 28 km or more and the longest was 56.7 km (2.8× the 20 km leg).
    Run120-24. Capped there by 1 run in 4 weeks. Left at the midpoint: the run covered the full 5 km leg, but at 63% in Zones 4-5, and older runs were all under 1.8 km.
    Recovery27Garmin training readiness, 2026-10-21 (🔴). Used because it is the latest score, dated today; the after-wake score on 10-20 was 1, which would make the overall 41.
    Consistency6050-69. Every week had training, but weekly time swung from 8.4 h to 4.0 h, swim appeared in 0 of 4 weeks and run in 1 of 4. Missed sessions can't be counted without a plan.
    Overall44 / 10018×0.2 + 85×0.3 + 12×0.25 + 27×0.10 + 60×0.15

    This is a

    baseline, not a verdict. Your race is next season with no date yet, so there is plenty of time to move it, and swim and run are where almost all of the points are.

    Key Takeaways

    1. Rest first. Readiness is red (27 today, 1 after waking yesterday). Train only once it's back to 40 or higher.

    Swimming is your limiter, and running is nearly missing. You had 0 swims and 1 run in 4 weeks. Start with two easy swims and one easy run-walk this week, and build from there.
    3.

    Slow the bike down. 64% of your ride time was in Zones 1-2 (target ≥75%), and 23% was in Zone 3 (target ≤10%). Keep HR under 150 on easy rides and 146 on easy runs.

    Four things I need from you: your race date, which lets me set the base, build and brick phases; a 0-100 difficulty rating for swim, bike and run; how many hours a week you can train, and on which days; and whether and when you can get to a pool. Want these sessions pushed to your Garmin calendar? The rides, the run-walk and the strength session can go up as workouts; the swims may have to come as text if Garmin rejects them. Say the word and I'll confirm each one with you before uploading.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    What it does

    Ask your agent how your triathlon training is going and this skill pulls your last four weeks from Garmin before it says anything. It totals sessions, distance, time and average heart rate for swim, bike and run (plus strength), works out what share of your training time each discipline gets, and adds up Garmin's per-activity time in heart-rate zones to check each sport against the 80/20 rule. It scores each discipline on volume, consistency, intensity quality and (if you tell it) how hard it feels, to name your limiter, and grades recovery green, yellow or red from training readiness, body battery, HRV and sleep, with readiness deciding when they disagree. Then it gives you this week: three to five focus items, a day-by-day schedule with key and easy sessions marked, one or two technique cues per discipline, brick guidance from about 12 weeks before your race until the taper, and, for a full assessment or when you ask, a 0-100 race-readiness score with five subscores. If you ask, and your Garmin connection can write workouts, it turns sessions into structured Garmin workouts and schedules them after you confirm.

    Why this instead of a prompt

    A plain "coach me for a triathlon" prompt gets you a generic plan, or numbers the model guessed. This skill pulls your data first and holds the analysis to written rubrics: discipline-share targets, 80/20 thresholds, a four-factor limiter matrix with its formulas, a traffic-light recovery check with a rule for mixed signals, and a weighted readiness formula with band-placement rules. What the $7 buys over a free coaching prompt is that structure: it reads Garmin's own readiness, HRV, sleep and per-activity time in zone instead of what you remember, and every score in the output can be checked against the rubric line by line. When a metric is unavailable it names the metric and leaves it out instead of estimating it. A red recovery status means the plan starts with rest. It asks for your race distance and date before it builds a periodized plan. And nothing is written to your Garmin account unless you ask and confirm.

    Key features

    • Finds whatever Garmin source is connected and maps each call by function (reference tool names come from the open-source Taxuspt/garmin_mcp server; prefixed names work). Without a server it can work from your own .fit files, Garmin Connect .csv export or Garmin account .json export, but that file mode is untested (see Known limitations).
    • Written fallbacks: when today's data has not synced it uses yesterday's and labels the date; when training status has no VO2 max it reads the VO2 max trend and reports the date the value was actually set; when body battery has no wake value it reads the sleep event.
    • Four-week discipline balance (share of time in swim, bike, run and strength, with average heart rate per discipline) against sprint/Olympic targets. Any of swim, bike or run under 15% is flagged as critically undertrained.
    • 80/20 intensity check per discipline from Garmin time-in-zone data summed over every activity with heart rate (the longest 20 per discipline if there are more), using your own zones when you have set them. More than 30% in Zone 4-5 is flagged as intensity overload. If your zones look wrong (for example a max HR above any heart rate in your data), it says so and gives the HR cap your data support.
    • Limiter scoring matrix with the formulas written out: volume against the minimum for your race distance, sessions per week, intensity quality, and perceived difficulty (from your own report; left unscored if you give none).
    • Recovery traffic light from training readiness, body battery, HRV and sleep. Stress and resting heart rate against its 7-day average are shown as context.
    • This week's plan: 3-5 focus items, a day-by-day schedule marking key and easy sessions, technique cues for swim, bike and run, and brick progressions from about 12 weeks out until the taper.
    • Race-readiness score (0-100) from swim, bike, run, recovery and consistency subscores, with the weights and the band-placement rules written out.
    • Garmin workout JSON templates (Z2 run, run 30/30 intervals, Z2 ride, bike tempo 3×10 min, swim drill and endurance 1500 m), each with a warmup and cooldown. Heart-rate zone targets on the steady run and bike steps; the 30-second run reps and all swim steps have no target (swim steps are distance-based). Uploads and schedules only after you confirm; without a write tool it gives the workouts as text.
    • Reference tables for base, build, peak and taper phases and minimum weekly volume by distance, sprint to Ironman.

    Who it is for

    Cyclists, runners and swimmers training for a first triathlon who want to see how far their other two sports are behind. Self-coached age-group triathletes on Garmin preparing for a sprint or Olympic race. Athletes with limited weekday time: tell it your schedule and constraints and the plan is built around them.

    How it is built

    One SKILL.md with a four-phase workflow (data collection, analysis, recommendations, optional workout upload) and a fixed output template, plus two reference documents. analysis-framework.md holds the zone definitions, minimum weekly volume by race distance, intensity scoring, the limiter matrix, the base/build/peak/taper phases and the readiness rubric with its weights. workout-templates.md holds Garmin workout JSON for run, bike and swim sessions with the sport, step, end-condition and target IDs. Markdown only: no scripts, no dependencies, and no network calls of its own. Not affiliated with or endorsed by Garmin, and separate from Garmin's own coaching features.

    Known limitations

    • It needs your Garmin data. With no Garmin tool and no exported files it stops and tells you what to connect; any advice after that is labeled as not based on your data.
    • What it can report depends on the Garmin server and your devices. In the demo on Taxuspt/garmin_mcp, endurance score returned a server error, fitness age returned nothing, training status had no VO2 max field (the skill then read the VO2 max trend), and the ride details it pulled had no cadence field. Each gap was reported as missing, not estimated. On that server the VO2 max trend stamps a value carried forward from an earlier measurement with the query's start date, so the skill has to look further back for the date the value was set. Early in the day, today's readiness may be a real-time update without last night's sleep and HRV, and today's sleep, HRV, body battery, stress and resting heart rate may not have synced yet; the skill then uses yesterday's values and labels them with their date.
    • File mode (no Garmin server) has not been tested. The Garmin Connect activities CSV is a one-row-per-activity summary, so from it alone the skill can report balance and volume but not time in zone: the intensity check and the intensity factor of the limiter need .fit files (and an agent that can parse them) or a Garmin MCP server. No .fit parser is bundled.
    • Discipline-share targets are written for sprint and Olympic distance. Minimum weekly volume for 70.3 and Ironman is included, but there are no share targets for those distances.
    • The limiter matrix only sees the last four weeks, so a discipline you trained earlier and then dropped can score below one you never built. Perceived difficulty is scored only from your own report. The intensity and limiter formulas are fixed, but placing you inside a race-readiness band is still a judgment call, so the agent has to state the band and its reason for every subscore. When Garmin has two readiness scores (an after-wake score and a later real-time update), the rubric does not say which one sets the recovery subscore; the agent has to say which it used.
    • Intensity analysis is heart-rate based and uses the zones on your watch. It does not analyze power or pace zones, and swims recorded without heart rate leave the swim intensity check with nothing to score. If your zones look wrong it flags them and gives the cap your data support, but correcting them in Garmin is up to you.
    • It plans one week. A periodized plan needs your race distance and date. Without your weekly hours, training days and pool access, the days in the plan are placeholders, and it asks for them.
    • Swim workout upload has not been verified end to end, and swimming is not in the reference server's documented upload sport list; if the upload fails, the swim is given as text. A brick is uploaded as two workouts on the same day.
    • Not medical advice. It does not diagnose anything. If you report pain, injury, illness, chest symptoms or dizziness, it stops prescribing that training and recommends seeing a medical professional. It does not ask about symptoms on its own, even when readiness is very low (in the demo, after-wake readiness was 1 and the result did not ask how the athlete felt), so tell it.
    • The demo below is one real run on Garmin data. It was checked against the source data afterwards, and a handful of dates, labels and wordings were corrected before posting; check key numbers in your own runs.

    It needs Garmin data, from a connected Garmin MCP server or from exported files, and stops if it has neither. What it can report depends on the server and your devices: in the demo on Taxuspt/garmin_mcp, endurance score returned an error, fitness age was empty, VO2 max was not in the training-status output (the skill read the VO2 max trend instead) and the ride details it pulled had no cadence field; each gap was reported as missing rather than estimated. That server's VO2 max trend stamps a carried-forward value with the query's start date, so the skill looks further back for the date the value was set. Early in the day, today's readiness may not include last night's sleep and HRV, and today's sleep, HRV and resting heart rate may not have synced yet; the skill then uses yesterday's values and labels their date. File mode has not been tested: a Garmin Connect activities CSV has per-activity summaries only, so the intensity check and the intensity part of the limiter need .fit files (and an agent that can parse them) or a Garmin MCP server, and no .fit parser is bundled. Discipline-share targets are for sprint and Olympic distance. The limiter score only sees the last four weeks, and placing you inside a race-readiness band is a judgment call the agent must explain; when Garmin has both an after-wake and a later readiness score, the rubric does not say which sets the recovery subscore. Intensity analysis is heart-rate based and uses your watch's zones, with no power or pace-zone analysis; if the zones look wrong it says so, but it cannot fix them for you. It plans one week at a time; a periodized plan needs your race distance and date, and without your schedule and pool access the plan's days are placeholders. Swim workout upload has not been verified end to end. Not medical advice, and it does not ask about illness or pain unless you raise it. Not affiliated with Garmin. The demo below is one real run on Garmin data. It was checked against the source data afterwards, and a handful of dates, labels and wordings were corrected before posting; check key numbers in your own runs.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 27 days ago

    Requires

    Garmin
    Garmin Or Garmin Data Export MCP

    Permissions

    Read Files

    Allowed Hosts

    connect.garmin.com

    the skill coaches from your own training history, so it has to read that history. It does this through the Garmin connection you already set up in your agent, or from files you exported and gave it. It ships no code and never contacts Garmin or any other service by itself. It writes something only when you ask for workouts on your Garmin calendar, and even then it shows you the workouts and waits for your confirmation before uploading. Your Garmin data goes only to the agent you run the skill in.

    Listed27 days ago

    What's inside

    Frequently Asked Questions

    It is the route the demo used and the only one tested. File mode has not been tested: you can give it activity .fit files, the Garmin Connect activities .csv, or the JSON files from a Garmin account data export, but the activities CSV has one summary row per activity, so the intensity check and the intensity part of the limiter need .fit files (and an agent that can parse them) or a Garmin MCP server. Training readiness and body battery are not in that CSV either. The skill names the missing metrics and works without them.

    Not unless you ask. The analysis only reads. If you want workouts on your watch, it shows them first and uploads only after you confirm. Each has a warmup and a cooldown, heart-rate zone targets on the steady run and bike steps (swim steps are distance-based with no target), and a "Tri Coach: ..." name so you can find it. The demo uploaded nothing.

    Yes, that is a common starting point. A discipline with no sessions is reported as 0% and flagged as critically undertrained, not skipped. In the demo the athlete had 0 swims and 1 run in four weeks, and the week's plan added two swims and one run-walk.

    It plans this week. For a periodized plan it first asks for your race distance and date, then works from the base, build, peak and taper phases and the minimum weekly volume for that distance in its reference. Bricks begin about 12 weeks out and continue until the taper.

    If recovery comes out red (for example, training readiness under 40), the plan starts with rest, with no exceptions. The skill is told never to prescribe training that could be dangerous. It is not medical advice and does not diagnose anything. If you report pain, injury, illness, chest symptoms or dizziness, it stops prescribing that training and recommends seeing a medical professional. It does not ask about symptoms on its own, so tell it if something feels off.

    No. It is not affiliated with or endorsed by Garmin, and it is separate from Garmin's own coaching features. It only reads your data through the Garmin connection you set up.

    New in Research & Analysis