Update to World War Watcher

{
  "description": "Brief the user on the Iran–US war from World War Watcher's curated, sourced data, with a citation for every claim. Use when the user asks what is happening in the war, for a daily or weekly briefing, or how the war is affecting oil, shipping, cloud infrastructure or weapon stocks. The user's own instructions about scope, length or format take precedence over this skill.",
  "included_files": [],
  "name": "war-briefing",
  "skill_md_contents": "---\nname: war-briefing\ndescription: Brief the user on the Iran–US war from World War Watcher's curated, sourced data, with a citation for every claim. Use when the user asks what is happening in the war, for a daily or weekly briefing, or how the war is affecting oil, shipping, cloud infrastructure or weapon stocks. The user's own instructions about scope, length or format take precedence over this skill.\n---\n\n# War briefing\n\nWorld War Watcher publishes daily dispatches, a dated event timeline, a graded source registry, a\n0–1 escalation score, US oil supply, Gulf cloud and connectivity status, submarine-cable status and\ncurated weapon stockpiles. Day 1 of the war is 2026-02-28; war day N is 2026-02-28 plus N−1 days.\n\nThe user's instructions override this skill whenever they differ.\n\n## \"Brief me on the war today\"\n\n1. `get_dispatch` with no day: the latest dispatch and its sections.\n2. `search_timeline` with `from` set two days before today: the newest dated events.\n3. `get_escalation_score` with `history_days: 7`: the score, its factors and the week's trend.\n4. `get_oil_supply`, when the briefing should cover energy.\n5. Optionally `render_situation_card`, when a visual helps.\n\nLead with events, not the score. When the score appears, say it measures current intensity and is\nnot a forecast. Cite each claim with the `url` of the result it came from.\n\n## \"How is X affecting Y\"\n\n1. Map Y to its data tool: oil → `get_oil_supply`; cloud, internet or cables →\n   `get_infrastructure_status`; interceptors or missiles → `get_weapon_stockpiles`.\n2. `search` for \"X Y\", then `fetch` the two most relevant passages.\n3. `search_timeline` for X to date the events.\n\nKeep correlation and attribution apart: a movement in the data that coincides with an event is not\nevidence the event caused it unless a passage says so, with its source.\n\n## Rules\n\n- Report not-found as not-found. A day without a dispatch, or a passage id that does not exist, is\n  absent, not pending.\n- Flag stale data: when a result has `stale: true`, say how old `asOf` is.\n- Attribute: timeline events carry `source_attribution`, and `quoted_text` is the quoted party's own\n  words. Present claims as the source's, not as settled fact.\n- Stockpile counts are curated estimates with a confidence grade and an assessment date; a null\n  count is not assessed, never zero.\n- Decline trading advice and forecasts of strikes, targets or casualties. For casualty totals, point\n  to the UN OCHA and UCDP datasets rather than estimating.\n- World War Watcher's data is CC BY-NC 4.0: cite it and do not present it as your own.\n"
}