Menu
Verify Strava MCP connectivity and capture athlete identity before flipping the integrations.strava.connected flag. Returns ok+athlete_id on success, classified error on failure.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Applies 1/2/3-strike adjustment rules to plan.json based on a single workout's analysis dict. Mutates plan only when thresholds fire. Called after every workout log.
Renders today's workout card from plan.json and daily_state.json as a Markdown block. Use for every /run-today invocation. No writes — pure read-and-render.
Conversationally captures a completed workout (duration, distance, RPE, HR, splits, notes) and writes it to workouts.json. Triggers analyze-workout and adapt-plan downstream. Use for /run-log.
Inserts a post-race or injury-flag recovery block into plan.json: 4 days rest + 3 easy jog days (post-race), or 3 rest + 1 recovery (red-flag-fatigue), or 7 rest days (injury). Use after /run-race-recap or when adapt-plan returns red_flag_recovery.
Web-search-backed Q&A for novel coaching questions outside the plan's standard logic: heat acclimation, recovery from illness, pacing strategies for unique courses. Use for /run-research and when the Coach cannot answer from training data alone.
Aggregates the past 7 days of completed workouts: total mileage, quality session adherence, fatigue indicators (RPE creep, HR drift). Decides hold/advance/recovery for the next week. Use for /run-week.
| name | probe-strava-connection |
| description | Verify Strava MCP connectivity and capture athlete identity before flipping the integrations.strava.connected flag. Returns ok+athlete_id on success, classified error on failure. |
Checks whether the Strava MCP server is available, calls mcp__strava__check-strava-connection to verify OAuth state, then mcp__strava__get-athlete-profile to capture athlete identity. Returns a structured result used by /run-init --connect strava to decide whether to flip users.json.integrations.strava.connected to true.
/run-init --connect strava.connected: true to users.json — no optimistic connection.Returns a dict in one of two shapes:
Success:
{ "ok": true, "athlete_id": 12345678, "username": "jrunner", "firstname": "Jordan" }
Failure:
{ "ok": false, "error": "<code>", "message": "<human-readable instructions>" }
See body.md for the full decision tree and user-facing messages for each failure mode.