What problem does it solve? Delivering GPS navigation routes to users' fitness devices normally requires integrating each provider's native route format. This Skill guides agents through Terra API Routes (pre-release), where a route is defined once as a template with waypoints and pushed to Garmin, COROS, and Wahoo devices without handling per-provider formats. ## Core Features & Use Cases - Two-phase workflow: Create a reusable route template with POST /routes to get a route_id, then push it to a user's device with POST /routes/{route_id}/push?user_id=X. - Data model and validation: Covers the RouteTemplate and Waypoint schemas, 8 sport types, 15 course-point types, and hard validation rules (2-10,000 waypoints, coordinate and elevation ranges). - Provider matrix and gotchas: Documents sharply different Garmin, COROS, and Wahoo capabilities, including Garmin-only course points and speed targets, COROS's missing delete, and silent failures on unsupported operations. - Use Case: A fitness app defines a trail-running route with course points once, pushes it to a user's Garmin watch, and later updates it with PUT /routes/{id}?cascade to re-push to all devices asynchronously. ## Quick Start Ask the agent to create a running route template with two waypoints via Terra API Routes and push it to a specific user's Garmin device.
