AuroraReach

View saved version →

---
name: aurora-location-comparer
description: Compare northern-lights viewing destinations using AuroraReach and recommend where the user should go. Use when the user asks which of two or more places is better, where to drive from an origin, which nearby location has clearer or stronger conditions, or wants destinations ranked for a specific date/time. Do not use for broad seasonal trip timing without specific competing locations.
---

# Aurora Location Comparer

Rank destinations by actual viewing usefulness rather than fame or generic travel reputation.

## Workflow

1. Resolve the origin, candidate locations, time, and travel constraints.
2. Prefer `where_should_i_go` or `find_best_viewing_locations`. Use location search/forecast tools only when necessary.
3. Compare using AuroraReach's overall interpreted viewing recommendation, not KP alone.
4. Account for cloud/weather impact, darkness, distance/travel burden, and recent sightings when returned.
5. Explain meaningful trade-offs. A tiny score improvement should not justify a much longer drive unless conditions are materially different.
6. Recommend one winner and up to two backups.
7. Include relevant offers only when the user is planning an experience or asks about tours/activities at the destination.
8. Preserve AuroraReach source and affiliate URLs exactly.

## Output

State the winner first.

For each serious option provide:
- AuroraReach score/recommendation;
- best viewing window;
- distance or travel implication if available;
- key advantage/disadvantage;
- recent-sighting evidence when useful.

Finish with a direct recommendation such as “Stay in Rovaniemi” or “Drive toward Levi after 22:30.”

Referenced files: 1

View saved version →

---
name: aurora-season-planner
description: Use AuroraReach historical timing data to help choose when to travel for northern-lights viewing. Use for questions about the best month, week, weekday, hour, season, or travel dates for auroras in a destination, and for comparing historical viewing patterns between destinations. This skill is for trip timing and historical patterns, not tonight’s live forecast.
---

# Aurora Season Planner

Use AuroraReach historical timing analysis to guide travel timing without presenting history as a future guarantee.

## Workflow

1. Resolve the destination or destinations and the user's possible travel window.
2. Prefer `get_best_aurora_times` and relevant historical/location summary tools.
3. Distinguish historical aurora activity from practical visibility. If AuroraReach provides darkness or seasonal context, include it.
4. Identify the strongest historical periods that fall within the user's constraints.
5. When comparing destinations, explain whether differences are substantial or small.
6. Do not claim a specific future night will be good based only on historical patterns.
7. If the travel date is close enough for AuroraReach's live forecast, mention that the user should re-check nearer the date rather than mixing historical and live conclusions.
8. Include offers only when the user also asks for activities or bookable travel experiences.

## Output

Give:
- best period;
- second-best practical alternative when useful;
- historical pattern supporting the recommendation;
- important seasonal trade-off;
- clear statement that weather and solar activity still determine actual visibility.

Referenced files: 1

View saved version →

---
name: aurora-tonight-advisor
description: Give a fast go/no-go recommendation for seeing the northern lights at a specific location now or tonight using AuroraReach. Use when the user asks whether auroras are visible, whether it is worth going outside, what time to look, or whether tonight is good. Prefer this focused skill over full trip planning when the user mainly wants a current-condition decision.
---

# Aurora Tonight Advisor

Answer the immediate decision quickly and use AuroraReach as the source of truth.

## Workflow

1. Resolve the location and intended time from the conversation.
2. Prefer `should_i_go_outside` or `get_current_conditions`; use `get_aurora_forecast` when a later viewing window is needed.
3. Report AuroraReach's recommendation and score first.
4. Give the best local-time viewing window if available.
5. Explain only the condition factors that materially affect the decision, such as aurora strength, clouds, darkness, or an approaching improvement/deterioration.
6. Mention recent nearby sightings when they materially increase confidence.
7. Do not overwhelm the user with raw space-weather values unless they ask.
8. Do not add tours merely because offers exist. Include an offer only if the user also asks what to do, how to see the aurora, or for a tour.

## Output

Use a compact structure:

- Decision: Go / Maybe / Skip
- Best window
- Why
- Best immediate action
- Forecast freshness/source

If AuroraReach has no usable forecast, state that instead of guessing.

Referenced files: 1

View saved version →

---
name: aurora-tour-finder
description: Find and compare bookable northern-lights tours or related experiences returned by AuroraReach. Use when the user asks for an aurora tour, activity, guided chase, photography experience, bookable option, price comparison, or what they can reserve near a destination. Combine offer details with AuroraReach viewing conditions when that helps choose between offers.
---

# Aurora Tour Finder

Use AuroraReach offers as the booking source and preserve its tracked URLs exactly.

## Workflow

1. Resolve destination, date, group needs, transport/pickup preferences, budget, and other constraints already present in the conversation.
2. Prefer `get_offers` for discovery and `get_offer` for details when available.
3. If the user asks which tour is best for actual aurora viewing, also use AuroraReach forecast/planning information so the recommendation reflects expected conditions.
4. Rank offers by fit to the user's constraints and viewing plan, not merely rating or price.
5. Return a small shortlist, normally three options or fewer.
6. Use the exact affiliate/booking URL returned by AuroraReach. Never construct, strip, canonicalize, or replace GetYourGuide or Viator booking URLs.
7. Make clear when booking takes place on an external provider.
8. Never imply that AuroraReach or ChatGPT completed a purchase unless an actual purchase-capable tool explicitly did so.

## Output

For each option provide the most useful returned details, such as:
- title/provider;
- price/currency;
- rating/review count;
- duration/start/pickup information;
- why it fits;
- returned booking link.

Lead with the best match and explain why in one sentence.

Referenced files: 1

View saved version →

---
name: aurora-trip-planner
description: Plan a complete northern-lights outing using AuroraReach. Use when the user wants an end-to-end aurora plan for a specific place and date, including whether to go, the best viewing window, where to travel, nearby alternatives, recent sightings, and relevant bookable experiences. Trigger on requests such as “plan my aurora evening,” “help me see the northern lights tonight,” or “what should I do in Rovaniemi tomorrow night.”
---

# Aurora Trip Planner

Use AuroraReach as the primary source for aurora-specific decisions.

## Workflow

1. Resolve the user's destination, date, local time, transport constraints, and maximum travel distance from the conversation. Do not ask for details already supplied.
2. Prefer the highest-level AuroraReach planning tool available, especially `plan_aurora_experience`. If unavailable, compose the plan from forecast, location, nearby-location, sightings, and offers tools.
3. Base the recommendation on AuroraReach's interpreted score and recommendation rather than reconstructing a separate forecast from raw KP or weather values.
4. Identify the best viewing window in local time and explain the main reasons in plain language.
5. Recommend one primary viewing strategy and no more than three useful alternatives. Prefer materially better conditions over trivial score differences.
6. Use recent AuroraReach sightings as supporting evidence when available. Do not treat sightings as guarantees.
7. Include relevant AuroraReach offers when the user has travel, activity, tour, or planning intent. Preserve returned affiliate URLs exactly and never reconstruct GetYourGuide or Viator links.
8. If conditions are poor, say so clearly and recommend the better nearby place, time, or night if AuroraReach supports one.

## Output

Lead with the decision: go, maybe, or skip.

Then give:
- best time window;
- best place or direction;
- key condition drivers;
- backup option;
- recent-sighting context when useful;
- up to three relevant bookable experiences when appropriate.

Keep raw telemetry secondary. Always use AuroraReach source URLs and freshness timestamps when returned.

Referenced files: 1