Managing Hydration

Use when a runner agent receives a distance update and must deplete water proportionally, or when the runner enters a hydration station and must decide whether to stop and rehydrate. Triggered by distance events and station events.

GoogleCloudPlatform 1d279a5 3 files · 3.6 KB Updated

File contents

Managing Hydration

The runner starts the race partially hydrated (typically 88-100, ability-correlated). Water depletes over distance and affects performance.

Instructions

  1. Deplete Hydration: When you receive a distance update, call deplete_water to reduce your hydration based on how far you ran:
    • Base loss: ~3.2 per mile (scaled by runner ability).
    • Fatigue growth rate: ~3.2% per mile of total distance run.
  2. Rehydrate at Stations: When you enter a hydration station, decide whether to call rehydrate based on your current hydration:
    • Hydration <= 40: always stop.
    • Hydration 41-60: stop ~50% of the time.
    • Hydration > 60: stop ~30% of the time.
    • If exhausted: always stop.
  3. Avoid Collapse: If hydration drops below 30, you become exhausted. If it drops below 10 while exhausted, you collapse and cannot continue.

Tools

  • deplete_water: Deplete hydration by the given amount. Tracks exhaustion and collapse automatically.
  • rehydrate: Rehydrate at a station (capped at 100).

Note: Call these tools directly (no prefix like "managing-hydration:").

googlecloudplatform/race-condition/tree/main/agents/runner/skills/managing-hydration commit 1d279a5d9a

Frequently asked questions

npx skillmds@latest add googlecloudplatform/managing-hydration