Activity
Mon
Wed
Fri
Sun
Sep
Oct
Nov
Dec
Jan
Feb
Mar
Apr
May
Jun
Jul
Aug
What is this?
Less
More
AI Automation Society
440.7k members • Free
Let's Get Creative
1.1k members • Free
Athlete AI Community
855 members • Free
3 contributions to Athlete AI Community
28d •
Push straight to your Garmin watch
Hey everyone — sharing something I put together for my own setup, might be useful for some of you. Skip this if it's already covered somewhere in here. If you built the plan-my-week skill from the challenge, you know the drill: your coach reads your recent training, decides the week, writes it out for you — and then you still had to manually type the whole thing into your watch. Session, pace, reps, rest. Every week. All the intelligence, none of the delivery. Closed that gap. Your coach can now push the planned session straight to your watch, fully structured, so it's already there when you walk out the door: warm-up, the reps, the pace or heart-rate-zone target, the rest between them, built in. You just press start. What it actually does: - Reads whatever your plan-my-week skill already wrote for the week - Translates the day's prescription into a real Garmin structured workout (intervals, targets, all of it) - Shows you the translation in plain English first, so you can catch anything before it's sent - Dry-runs the exact payload — nothing touches your Garmin account until you say so - Only pushes for real after you explicitly confirm Prerequisites (you need both of these already): 1. Garmin already connected via the sync_garmin.py setup from the earlier guide in this group — this reuses that same login, no new setup needed. 2. Your plan-my-week skill already up and running and producing your weekly plan file. How to build it — same two-prompt pattern as everything else here: 1. An implementation prompt that builds the raw push capability (push_workout.py, dry-run by default) 2. A skill prompt that wires it to your actual weekly plan (a separate push-workout skill, kept deliberately apart from plan-my-week — one decides the training, the other only delivers it) Both prompts below. A few things I learned building this, in case it saves you time: - Garmin has no official API for creating workouts, but the same authenticated session your sync script already has can hit the real
1 like • 28d
Prompt 2 — Skill (paste into Claude Code) Prerequisite stated at the top: you need Prompt 1's push_workout.py already built and dry-run tested, and your plan-my-week skill already producing a dated weekly plan file with a table of daily sessions. I want a new Claude Skill, completely separate from my plan-my-week skill, that takes the session plan-my-week already decided and pushes it to my Garmin watch. Call it push-workout. Keep the two skills strictly separate: plan-my-week only decides and saves the week — it should never touch Garmin at all. push-workout only translates and sends — it never re-decides the training, it trusts whatever is already written in the saved file. Build it like this: 1. Read my own plan-my-week output (the current week file) to learn the exact way I write a day's session: how I write pace, how I write intervals/reps, how I write warm-up/cool-down, how I write a continuous or long run. Don't assume a fixed format — look at a real example from my own files first, then build the translation rules around what's actually there. 2. Write the SKILL.md so that it: - Finds the right week file (most recent by default, or a specific one I name) and reads the session(s) I want to push. - Translates each planned session into the step format push_workout.py expects (warm-up/cool-down by duration, intervals as a repeat group with rest between reps, continuous/long runs as a single step by duration or distance, pace or HR-zone target). - Never invents a pace tolerance my plan didn't give — a single target pace becomes a zero-width range (min == max); only use a real range when the plan already gave one, and never mix up which side is "faster" vs "slower" in seconds/km. - Skips rest days and non-running cross-training — this skill only pushes structured running sessions. - Before generating anything, shows me the translation in plain language (e.g. "Tuesday — warm-up 10 min, then 5x [400m at 5:51/km + 2 min jog], then cool-down 5 min") and asks me to confirm it's right — via
1 like • 28d
[attachments]
28d •
It's alive!
I've already added Garmin to it. I'm also working on a feature that will send my workouts directly to my watch, just like the 'plan-my-week' skill does. As soon as I figure that out, I'll share it here
1 like • 28d
Some improvments
Jun 6 •
Welcome to Athlete AI. Introduce Yourself!
Glad you're here. I'm Kevin, an ultrarunner & triathlete (Leadville 100 was my most fun race). I'm not a tech guru. I got curious about AI, realized I could build training tools tailored exactly to me from my own data, and it actually worked. Now I want to teach you to do the same and connect with people building cool things in fitness with AI. That's the whole idea: learn something genuinely interesting, build stuff that's truly yours, and do it alongside like-minded people. Zero coding required. Five steps to start: 1. Introduce yourself in the feed. Something like: "Hi, I'm Steve, I run trail ultras and can't wait to build with AI!" 2. Complete the intro poll so we know we can build the content around what you want: Athlete AI Poll 3. Watch Start Here course (top of the Classroom). Two minutes. 4. Do Day 0 in the 7-Day Challenge: Set Up Your Workshop. 5. Post in Wins as you finish each day, tagged (#Day0Ready). We celebrate every one. The setup day is the hardest part, and we get everyone through it. Stuck? Post what you tried and someone (often me) will get you unstuck. Let's build. Follow the road to The Rut.
2 likes • 29d
Greetings from Brazil. I'm an AI enthusiast and a beginner runner. I hope this helps me unlock my half marathon goal 🏃
1-3 of 3