trainingpeaks_skill

This skill retrieves real-time TrainingPeaks metrics and workouts, enabling seamless coaching insights and performance tracking across endurance disciplines.

Python

2.5k

GitHub Stars

2

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill trainingpeaks

_meta.json284 B
SKILL.md4.7 KB

Overview

This skill provides command-line access to TrainingPeaks internals, letting you pull real-time training plans, workouts, fitness metrics (CTL/ATL/TSB), and personal records using cookie-based authentication. It requires no API key and runs with pure Python standard library code. Use it to archive, inspect, or script athlete data from TrainingPeaks quickly and reliably.

How this skill works

Authenticate by extracting the Production_tpAuth cookie from your browser and running the auth command or setting the TP_AUTH_COOKIE environment variable. The skill exchanges the cookie for a short-lived Bearer token, caches credentials and athlete info in ~/.trainingpeaks, and makes rate-limited requests to TrainingPeaks endpoints to fetch workouts, workout details, fitness time series, and PRs. Outputs are human-readable by default, with a --json flag for raw responses suitable for automation.

When to use it

Backup or archive an athlete's TrainingPeaks data locally or to another system.
Run scheduled scripts to pull daily fitness (CTL/ATL/TSB) for dashboards or alerts.
Export workouts and workout details for analysis, coaching reviews, or race prep.
Fetch ranked personal records (PRs) by sport and metric for athlete progress reports.
Integrate TrainingPeaks data into multi-tool coaching workflows (cycling, running, swim).

Best practices

Store the Production_tpAuth cookie securely and use file permissions (0600) as recommended.
Use the --json flag when scripting or piping output to other tools to avoid parsing human tables.
Keep queries to a maximum 90-day window for workouts to stay within API design limits.
Respect the built-in rate limiting (≈150ms between requests) when building loops or bulk exports.
Refresh cookies when prompted; tokens auto-refresh from the stored cookie but expired cookies require re-authentication.

Example use cases

Daily cron job that pulls CTL/ATL/TSB and updates a coach dashboard for training load monitoring.
Export completed workouts for a specific month to import into a third-party analytics tool.
Retrieve a single workout with coach comments and intervals for athlete feedback or race debrief.
Generate a list of top time-trial power PRs for bike training periodization and goal setting.
Archive an athlete account (profile, workouts, tokens) before account changes or migration.

FAQ

No. The skill uses your browser Production_tpAuth cookie to obtain a Bearer token; no API key is required.

Where are credentials stored and how long are tokens valid?

Credentials and cookie are stored under ~/.trainingpeaks with 0600 permissions. Bearer tokens last about an hour and are auto-refreshed from the stored cookie.