route-researcher

Route Researcher

Research mountain peaks across North America and generate comprehensive route beta reports combining data from multiple sources including PeakBagger, SummitPost, WTA, AllTrails, weather forecasts, avalanche conditions, and trip reports.

Data Sources: This skill aggregates information from specialized mountaineering websites (PeakBagger, SummitPost, Washington Trails Association, AllTrails, The Mountaineers, and regional avalanche centers). The quality of the generated report depends on the availability of information on these sources. If your target peak lacks coverage on these websites, the report may contain limited details. The skill works best for well-documented peaks in North America.

When to Use This Skill

Use this skill when the user requests:

• Research on a specific mountain peak
• Route beta or climbing information
• Trip planning information for peaks
• Current conditions for mountaineering objectives

Examples:

• "Research Mt Baker"
• "I'm planning to climb Sahale Peak next month, can you research the route?"
• "Generate route beta for Forbidden Peak"

Progress Checklist

Research Progress:

• [ ] Phase 1: Peak Identification (peak validated, ID obtained)
• [ ] Phase 2: Peak Information Retrieval (coordinates and details obtained)
• [ ] Phase 3: Data Gathering (parallel execution)
• [ ] Phase 3a: Python conditions fetch (weather, air quality, daylight, avalanche, peakbagger stats/ascents)
• [ ] Phase 3b: Researcher agents (3 in parallel - web sources + trip reports)
• [ ] Phase 3c: Results aggregated
• [ ] Phase 3d: Access/permits (inline WebSearch)
• [ ] Phase 4: Route Analysis (synthesize route, crux, hazards)
• [ ] Phase 5: Report Generation (Report Writer agent)
• [ ] Phase 6: Report Review & Validation (Report Reviewer agent)
• [ ] Phase 7: Completion (user notified, next steps provided)

Orchestration Workflow

Phase 1: Peak Identification

Goal: Identify and validate the specific peak to research.

1. Extract Peak Name from user message
2. Look for peak names, mountain names, or climbing objectives
3. Common patterns: "Mt Baker", "Mount Rainier", "Sahale Peak", etc.

1. Search PeakBagger using peakbagger-cli:

``bash uvx --with patchright --from "git+https://github.com/dreamiurg/peakbagger-cli.git@v1.10.0" peakbagger peak search "{peak_name}" --format json ``

• Parse JSON output to extract peak matches
• Each result includes: peak_id, name, elevation (feet/meters), location, url

1. Handle Multiple Matches:
2. If multiple peaks found: Use AskUserQuestion to present options
3. For each option, show: peak name, elevation, location, AND PeakBagger URL
4. Format each option description as: "[Peak Name] ([Elevation], [Location]) - [PeakBagger URL]"
5. This allows user to click through and verify the correct peak
6. Let user select the correct peak
7. Provide "Other" option if none match

• If single match found: Confirm with user
• Present confirmation message with peak details and PeakBagger link
• Show: "Found: [Peak Name] ([Elevation], [Location])"
• Include PeakBagger URL in the message so user can verify: "[PeakBagger URL]"
• Use AskUserQuestion: "Is this the correct peak? You can verify at [PeakBagger URL]"

• If no matches found:
• Try peak name variations systematically (see "Peak Name Variations" section):
• Word order reversal: "Mountain Pratt" → "Pratt Mountain"
• Title variations: Mt/Mount, St/Saint
• Add location: Include state or range name
• Remove titles: Try just the core name
• Run multiple searches in parallel with different variations
• Combine results and present best matches to user
• If still no results, use AskUserQuestion to ask for:
• A different peak name variation
• Direct PeakBagger peak ID or URL
• General PeakBagger search

1. Extract Peak ID:
2. From search results JSON, extract the peak_id field
3. Store for use in subsequent peakbagger-cli commands
4. Also store the PeakBagger URL for reference links

Phase 2: Peak Information Retrieval

Goal: Get detailed peak information and coordinates needed for location-based data gathering.

This phase must complete before Phase 3, as coordinates are required for weather, daylight, and avalanche data.

Retrieve detailed peak information using the peak ID from Phase 1:

uvx --with patchright --from "git+https://github.com/dreamiurg/peakbagger-cli.git@v1.10.0" peakbagger peak show {peak_id} --format json

This returns structured JSON with:

• Peak name and alternate names
• Elevation (feet and meters)
• Prominence (feet and meters)
• Isolation (miles and kilometers)
• Coordinates (latitude, longitude in decimal degrees)
• Location (county, state, country)
• Routes (if available): trailhead, distance, vertical gain
• Peak list memberships and rankings
• Standard route description (if available in routes data)

Error Handling:

• If peakbagger-cli fails: Fall back to WebSearch/WebFetch and note in "Information Gaps"
• If specific fields missing in JSON: Mark as "Not available" in gaps section
• Rate limiting: Built into peakbagger-cli (default 2 second delay)

Once coordinates are obtained from this step, immediately proceed to Phase 3.

Phase 3: Data Gathering

Goal: Gather comprehensive route information from all available sources.

Execution Strategy: Run Python script for deterministic API data + dispatch specialized agents in parallel for web research. This hybrid approach minimizes token usage while maximizing parallelism.

Step 3A: Fetch Conditions Data (Python Script)

Run the conditions fetcher script to gather all API-based data:

cd "{repo_root}/skills/route-researcher/tools"
uv run python fetch_conditions.py \
  --coordinates "{latitude},{longitude}" \
  --elevation {elevation_m} \
  --peak-name "{peak_name}" \
  --peak-id {peak_id} \
  --trailhead "{trailhead_lat},{trailhead_lon}" \
  --distance-mi {round_trip_distance_mi} \
  --gain-ft {total_gain_ft} \
  --start-time "{HH:MM}" \
  --waypoint "{lat1},{lon1}" --waypoint "{lat2},{lon2}"

Optional args: --trailhead enables multi-county path sampling (trailhead→summit); hospital/ranger lookups always run from the summit regardless; --distance-mi/--gain-ft enable time_estimates; --start-time (with distance + gain) enables itinerary; --waypoint (2+) enables bearings.

This returns JSON with:

• weather: 7-day forecast with temperatures, precipitation, freezing levels; each day includes snow_line_note (human-readable framing of freezing level as snow line) and near_summit (bool: true when freezing level within 2000 ft of summit)
• air_quality: AQI ratings and any concerns
• daylight: Full twilight table — astronomical_dawn, nautical_dawn, civil_twilight (dawn), sunrise, sunset, civil_dusk, nautical_dusk, astronomical_dusk; values are null at high latitudes when sun doesn't reach threshold (white nights); daylight_hours, timezone
• time_estimates: Roped/unroped + 3-tier pacing (roped_hr, unroped_hr, fast_hr, moderate_hr, leisurely_hr) — only present when --distance-mi and --gain-ft CLI args are provided
• itinerary: Trip schedule with safety signals (start_time, summit_eta, turnaround_by, return_eta, total_hr, after_dark bool, dusk_cutoff, note) — only present when --start-time, --distance-mi, AND --gain-ft are all provided; after_dark: true is a safety warning that must be prominently surfaced; total_hr is the full round-trip duration in hours
• bearings: Navigation bearings between waypoints (segments[] with bearing_deg, distance_mi, cumulative_distance_mi; total_distance_mi) — only present when 2 or more --waypoint "lat,lon" args are provided
• avalanche: NWAC region and URL for manual chec