← AuroraReachCONTENT HISTORY

Update to AuroraReach

Snapshot Sep 30, 2026 · 23:02 UTC · version 1.0.0

Collection source: not recorded for this historical snapshot.

WHAT CHANGED · RULE-BASED ANALYSIS

First saved snapshot

No earlier snapshot is available to establish a change.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "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.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 114
    }
  ],
  "skill_md_contents": "---\nname: aurora-season-planner\ndescription: 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.\n---\n\n# Aurora Season Planner\n\nUse AuroraReach historical timing analysis to guide travel timing without presenting history as a future guarantee.\n\n## Workflow\n\n1. Resolve the destination or destinations and the user's possible travel window.\n2. Prefer `get_best_aurora_times` and relevant historical/location summary tools.\n3. Distinguish historical aurora activity from practical visibility. If AuroraReach provides darkness or seasonal context, include it.\n4. Identify the strongest historical periods that fall within the user's constraints.\n5. When comparing destinations, explain whether differences are substantial or small.\n6. Do not claim a specific future night will be good based only on historical patterns.\n7. 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.\n8. Include offers only when the user also asks for activities or bookable travel experiences.\n\n## Output\n\nGive:\n- best period;\n- second-best practical alternative when useful;\n- historical pattern supporting the recommendation;\n- important seasonal trade-off;\n- clear statement that weather and solar activity still determine actual visibility.\n"
}

SHA-256: 8003f22813042a61b068c84c74b68258b251d6373f43dd19a42e88ce3abd233c