← AuroraReachCONTENT HISTORYWHAT CHANGED · RULE-BASED ANALYSIS
Update to AuroraReach
Snapshot Sep 30, 2026 · 23:02 UTC · version 1.0.0
Collection source: not recorded for this historical snapshot.
First saved snapshot
No earlier snapshot is available to establish a change.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"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.",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 111
}
],
"skill_md_contents": "---\nname: aurora-location-comparer\ndescription: 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.\n---\n\n# Aurora Location Comparer\n\nRank destinations by actual viewing usefulness rather than fame or generic travel reputation.\n\n## Workflow\n\n1. Resolve the origin, candidate locations, time, and travel constraints.\n2. Prefer `where_should_i_go` or `find_best_viewing_locations`. Use location search/forecast tools only when necessary.\n3. Compare using AuroraReach's overall interpreted viewing recommendation, not KP alone.\n4. Account for cloud/weather impact, darkness, distance/travel burden, and recent sightings when returned.\n5. Explain meaningful trade-offs. A tiny score improvement should not justify a much longer drive unless conditions are materially different.\n6. Recommend one winner and up to two backups.\n7. Include relevant offers only when the user is planning an experience or asks about tours/activities at the destination.\n8. Preserve AuroraReach source and affiliate URLs exactly.\n\n## Output\n\nState the winner first.\n\nFor each serious option provide:\n- AuroraReach score/recommendation;\n- best viewing window;\n- distance or travel implication if available;\n- key advantage/disadvantage;\n- recent-sighting evidence when useful.\n\nFinish with a direct recommendation such as “Stay in Rovaniemi” or “Drive toward Levi after 22:30.”\n"
}SHA-256: 8ec58d0a395cd9cd21dbecbbaf70ace248fbf596c81a66ac37783de74207d448