← Sugra APICONTENT HISTORY

Update to Sugra API

Snapshot Oct 24, 2026 · 18:04 UTC · version 1.2.1

Collection source: downloaded plugin package.

WHAT CHANGED

First saved snapshot

No earlier snapshot is available to establish a change.

Save Sugra API and check future changes in Following.

Up to 10 plugins free · no card required.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Compose one briefing from two or three Sugra directions over HTTPS or MCP. Use when a question spans Finance, Macro, Entity, Net Atlas, News, Earth, or Research and one operation is not enough.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 241
    }
  ],
  "name": "cross-domain-briefing",
  "skill_md_contents": "---\nname: cross-domain-briefing\ndescription: Compose one briefing from two or three Sugra directions over HTTPS or MCP. Use when a question spans Finance, Macro, Entity, Net Atlas, News, Earth, or Research and one operation is not enough.\nlicense: MIT\n---\n\n# Cross-domain briefing\n\nSplit the question. Call two or three operations. Do not invent a combined index. HTTP and MCP are both valid; use the surface already connected. Confirm each operation on https://docs.sugra.ai.\n\n## Pattern\n\n1. Split the question into 2-3 concrete asks (place, series, snapshot). Name the directions involved (Finance, Macro, Entity, Net Atlas, News, Earth, Research).\n2. For each ask, discover then call (`discover-and-call`). Prefer sovereign or intergovernmental sources when the catalog offers them.\n3. Keep units, geography, and clocks separate. Do not blend a port throughput z-score with a weather reading into one invented number.\n4. Quote each figure with its source from `meta` (or `_meta` on a flat payload) and its date: an `as_of` when present (in a record, in `data`, or in `meta`), `meta.period`, or a `data_time` the source stated, never one that fell back to the response time. With none of them, say the source time is unavailable (see `envelope-and-attribution`).\n5. Close with what the catalog did not cover, not a prediction.\n\n## Example shape (not a canned path list)\n\n\"What is happening around a chokepoint this week?\" can be three calls: port throughput (Sugra Earth / transport), conditions at a coordinate on the route (Sugra Earth), and one related sovereign or intergovernmental series docs.sugra.ai actually lists. Discover, call, present side by side.\n\nThe MCP prompt `earth_conditions` is a one-coordinate recipe for weather, air quality, and nearby hazards. This skill is the longer form when those conditions are only one pane.\n\nDo not add per-endpoint MCP tools. Do not treat screening as a briefing source unless the question is about a named party. On MCP, stay on the gateway tools so the briefing works on stdio and hosted alike. Do not frame the output as investment, legal, or routing advice.\n"
}

SHA-256 of public snapshot: f9ccb75b0922d44f53c0867cb1c4e09d157d13d7916c0b60eec25bdd65da2122