Strava CLI Skill for Muse
Ask Muse about your Strava data — activities, stats, segments, routes, gear
- What
- Ask Muse about your Strava data — activities, stats, segments, routes, gear
- Cost
- Free
- Needs
- the strava-cli installed via the repo's install script — review the script at https://github.com/eddmann/strava-cli/blob/main/install.sh YOURSELF before piping it to sh (the skill installs with curl | sh); then authenticate with `strava auth login`, which needs a STRAVA_CLIENT_ID and STRAVA_CLIENT_SECRET from a free Strava API app you create yourself. Store the credentials in the agent's secure vault — never paste secrets here. Your own Strava account with training data, obviously.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
⚠️ **Security warning / Avertissement de sécurité** — the prerequisites install the companion CLI with `curl | sh` from the repo; review the install script yourself before running it. Curated by Skill Harbor — a free, open-source skill (MIT) by @eddmann, listed here with credit to its creator. Turns Muse into a query interface for your own Strava fitness data via the `strava` CLI: recent and filtered activity lists, per-activity detail (streams, laps, zones, comments, kudos), athlete profile and year-to-date/all-time stats, heart-rate and power zones, starred and explored segments with efforts, routes (list, detail, GPX/TCX export), clubs and their activities, and gear inventory — with `jq` patterns for common questions (this month's runs, total distance) and a one-call `strava context` snapshot (athlete, stats, gear, clubs, recent activities). Discovered via skills.sh. Honest note: the skill is a command reference for the strava-cli tool — you must install the CLI and complete Strava OAuth yourself (creating a Strava API app for your client ID/secret is free, but it is a developer-flavoured setup: `strava auth login`), and it reads your private fitness data, so treat the credential like a password and store it in the agent's secure vault, never in code or prompts. Skill Harbor never reviews the code, review it yourself before use. Not verified.
Version:
Install
Prerequisites: the strava-cli installed via the repo's install script — review the script at https://github.com/eddmann/strava-cli/blob/main/install.sh YOURSELF before piping it to sh (the skill installs with curl | sh); then authenticate with `strava auth login`, which needs a STRAVA_CLIENT_ID and STRAVA_CLIENT_SECRET from a free Strava API app you create yourself. Store the credentials in the agent's secure vault — never paste secrets here. Your own Strava account with training data, obviously. Install "Strava CLI Skill for Muse" for me. A command reference for the strava-cli tool that turns Muse into a query interface for my Strava data: activities (list, detail, streams, laps, zones), athlete profile and stats, HR/power zones, segments and efforts, routes with GPX/TCX export, clubs, gear, plus jq patterns for common questions and a one-call `strava context` snapshot. Repository: https://github.com/eddmann/strava-cli 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. The install script uses curl | sh — verify it only installs the CLI binary and does nothing else. STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "strava". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. run the install script after reviewing it, create my Strava API app, and run `strava auth login`). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.