zxt6991-source

Operate the local Fitness Agent CLI for Strava and Obsidian workflows. Use when Codex needs to authenticate with Strava, list or fetch Strava activities, export workout data as Obsidian-compatible Markdown, configure a local Obsidian vault path, or write/sync workout notes into a vault from the local fitness-agent project.

Analyze Strava-derived fitness notes that already exist in an Obsidian vault, then generate deeper dashboards, proxy training-load metrics, trend reports, and visual summaries. Use when the user wants post-sync analysis of existing workout notes rather than fetching new data from Strava.

Create forward-looking training plans from Strava-derived fitness notes already stored in an Obsidian vault. Use when the user wants a realistic next-week or next-two-week plan generated from recent load, consistency, sport mix, and recovery signals in their existing notes.

Operate the local Fitness Agent CLI for Strava and Obsidian workflows. Use when Codex needs to authenticate with Strava, list or fetch Strava activities, export workout data as Obsidian-compatible Markdown, configure a local Obsidian vault path, or write/sync workout notes into a vault from the local fitness-agent project.

Analyze Strava-derived fitness notes that already exist in an Obsidian vault, then generate deeper dashboards, proxy training-load metrics, trend reports, and visual summaries. Use when the user wants post-sync analysis of existing workout notes rather than fetching new data from Strava.

Create forward-looking training plans from Strava-derived fitness notes already stored in an Obsidian vault. Use when the user wants a realistic next-week or next-two-week plan generated from recent load, consistency, sport mix, and recovery signals in their existing notes.