- Home
- Skills
- Workflow Automation
- Fix Garmin's Inflated Climb for Magene, Wahoo & Bryton Rides
Works with the AI Agents you already use
Fix Garmin's Inflated Climb for Magene, Wahoo & Bryton Rides
Uploads a .fit from a non-Garmin bike computer to Garmin Connect and fixes the two things Garmin gets wrong: climb inflated 10–70× by Elevation Correction, and rides filed as "Other" instead of cycling.
$5
Fix Garmin's Inflated Climb for Magene, Wahoo & Bryton Rides
Example session with this skill installed
My Magene C506 ride from last Thursday shows 2,445 m of climbing on Garmin. The ride was flat. Here's the .fit: upload it to Garmin and fix the elevation and the activity type.
- Read your context and instructions
- Compiled the fix garmin s
Summary
Uploaded the ride unmodified, waited for Garmin to finish processing, turned Elevation Correction off for that activity and set the type to cycling. Climb went from Garmin's inflated
2,445 m back to the device's 65 m; type went from
other to cycling. Your local .fit was not touched.
First run
$ python3 scripts/magene_to_garmin.py ~/Downloads/MAGENE_C506SE_2026-07-24_212843.fit
=== MAGENE_C506SE_2026-07-24_212843.fit ===
start (GMT): 2026-07-24 13:28:43
uploading... uploaded
activity 2379…: elevationCorrected=True type=other gain=2445.0
elevation: correction OFF -> gain 65.0 (was 2445.0)
type: other -> cycling
https://connect.garmin.com/modern/activity/2379…
Done.
The device value (65 m) equals the file's own session.total_ascent, which is the correctness check.
Running it again is safe
Second run on the same ride, captured while preparing this listing:
$ python3 scripts/magene_to_garmin.py --no-upload ~/Downloads/MAGENE_C506SE_2026-07-24_212843.fit
=== MAGENE_C506SE_2026-07-24_212843.fit ===
start (GMT): 2026-07-24 13:28:43
activity 2379…: elevationCorrected=False type=cycling gain=65.0
elevation: correction already off - no change
type: already cycling - no change
https://connect.garmin.com/modern/activity/2379…
Done.
Nothing was re-uploaded and nothing was toggled back.
Next steps
- Batch-fix a whole export:
python3 scripts/magene_to_garmin.py ~/Downloads - Fix elevation only and leave the type alone:
--type none - Ride already on Garmin via the phone app: use
--no-uploadwith the original .fit so it can be matched by start time.
Connects securely to your tools. The creator never sees your data.
About this skill
What it does
Garmin Connect only trusts barometric altitude from devices it recognizes as Garmin barometric units. A Magene, iGPSPORT, Bryton, Wahoo, COROS or Hammerhead file gets silently run through server-side Elevation Correction: the file's altitude is thrown away and climb is recomputed from a GPS-to-terrain lookup. Over bridges, in cities and on rough DEM tiles that produces climb figures 10 to 70 times too high (a real 65 m ride reported as 2,445 m). Rides recorded in navigate/route-follow mode arrive as activity type "Other".
This skill uploads your .fit unmodified, waits for Garmin to finish processing, turns Elevation Correction off for that activity (reverting climb to the device's own value), and sets the type to cycling. Both changes are server-side and reversible. It can also fix rides that are already on your account, and batch-process a whole folder.
Why this instead of a prompt
Two obvious fixes do not work and this skill saves you from re-deriving that: editing the .fit to declare the device does nothing (Garmin already reads the manufacturer and corrects anyway), and "fixing" the altitude stream does nothing (Garmin ignores it entirely). The only reliable fix is a per-activity toggle on Garmin's server, and there is no account-wide setting. The bundled script knows the endpoints, the timing (Garmin applies correction a few seconds after import, so toggling too early flips it the wrong way), the duplicate trap (Garmin does not dedupe uploads by start time), and the filename trap (anything not ending exactly in .fit gets a 403).
Key features
- One command: upload, wait, disable correction, set type, print before/after climb and the activity link.
- Idempotent: re-running never flips a fixed ride back and never re-uploads a ride that already exists.
- --no-upload mode to fix rides already on the account; folder mode to batch an export.
- Never edits your local .fit file.
- Uses an existing garth token store; no password is stored by the script.
- Documents every gotcha so your agent can adapt it if Garmin changes an endpoint.
Who it is for
Riders on Magene, iGPSPORT, Bryton, Wahoo, COROS or Hammerhead who keep their training history on Garmin Connect and are tired of 2,000 m "climbs" on flat rides. Especially useful for Chinese-brand head units, which Garmin never recognizes as barometric. The problem explanation also exists in Chinese in the linked repository.
Known limitations
- Needs a garth token store at ~/.garminconnect created once by any garth/garminconnect login (the skill explains how; MFA is supported by garth).
- Garmin's private Connect endpoints can change without notice. The script uses three of them and documents each so it can be repaired.
- Not for real Garmin devices (Edge, Forerunner, Fenix): those are already trusted and need no fix.
- A ride uploaded by another path (phone app, Strava sync) is matched by start time; if the start time differs by more than a few seconds the script will tell you it could not locate it.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Workflow Automation.
Needs a one-time garth login to create ~/.garminconnect. Uses three private Garmin Connect endpoints that can change without notice (each is documented in the skill). Not needed for real Garmin devices. Rides are matched by start time, so a ride uploaded by another path with a shifted start time will be reported as not found rather than guessed.
How to use
- 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
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
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
- Accounts
Garmin
- Software
Python 3.9+fitdecodegarth
garth keeps your Garmin Connect login token in ~/.garminconnect.
Permissions
Allowed Hosts
Shell runs the bundled Python script. File read is for the .fit files the user points it at and the garth token store. Network access is to Garmin Connect only, using the user's own account, to upload the file and toggle two settings on their own activity. Nothing else is contacted and the local .fit is never modified.