菜单
Verify Garmin Connect MCP connectivity and capture user identity before flipping the integrations.garmin.connected flag. Returns ok+garmin_user_id on success, classified error on failure.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 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-garmin-connection |
| description | Verify Garmin Connect MCP connectivity and capture user identity before flipping the integrations.garmin.connected flag. Returns ok+garmin_user_id on success, classified error on failure. |
Checks whether the garmin-givemydata MCP server is loaded and whether its local SQLite database has been seeded by an initial sync. Calls mcp__garmin__garmin_user_profile to verify the DB is populated and capture the runner's Garmin profile identity. Returns a structured result used by /run-init --connect garmin to decide whether to flip users.json.integrations.garmin.connected to true.
/run-init --connect garmin.connected: true to users.json — no optimistic connection.Returns a dict in one of two shapes:
Success:
{ "ok": true, "garmin_user_id": "123456789", "display_name": "Wilson Wang", "email": "wilson@example.com" }
Failure:
{ "ok": false, "error": "mcp_unavailable" | "db_empty" | "unknown", "message": "<human-readable instructions>" }
See body.md for the full decision tree and user-facing messages for each failure mode.