← 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-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.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 112
    }
  ],
  "skill_md_contents": "---\nname: aurora-tonight-advisor\ndescription: 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.\n---\n\n# Aurora Tonight Advisor\n\nAnswer the immediate decision quickly and use AuroraReach as the source of truth.\n\n## Workflow\n\n1. Resolve the location and intended time from the conversation.\n2. Prefer `should_i_go_outside` or `get_current_conditions`; use `get_aurora_forecast` when a later viewing window is needed.\n3. Report AuroraReach's recommendation and score first.\n4. Give the best local-time viewing window if available.\n5. Explain only the condition factors that materially affect the decision, such as aurora strength, clouds, darkness, or an approaching improvement/deterioration.\n6. Mention recent nearby sightings when they materially increase confidence.\n7. Do not overwhelm the user with raw space-weather values unless they ask.\n8. 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.\n\n## Output\n\nUse a compact structure:\n\n- Decision: Go / Maybe / Skip\n- Best window\n- Why\n- Best immediate action\n- Forecast freshness/source\n\nIf AuroraReach has no usable forecast, state that instead of guessing.\n"
}

SHA-256: e43830119b4f08f5adc9db66a3434873d6861e09f381b24c2005a17cdf8c42e3