emem-locate-and-recall

emem-locate-and-recall

Network use. The commands in this skill send and receive JSON (and, where a step says so, an image or a raster file) to https://emem.dev only, the service the plugin's MCP server connects to. Nothing they download is executed. The files under scripts/ read local files and make no network calls.

Two REST calls turn a place name into signed facts. Each fact comes back with its own emem:fact: token, so the number never has to travel without its citation.

When to invoke

The user asks about a measurable geospatial value at a named place:

• "What's the current 2 m air temperature in Bengaluru?"
• "Show me the NDVI in the Sundarbans."
• "What's the elevation of Mount Kilimanjaro?"

If you already hold a cell64 (a string like defi.zb493.zezo.zcb35), skip step 1. For an extent rather than a point, use emem-recall-polygon. For a picture, GET https://emem.dev/v1/cells/<cell64>/scene.png.

Step 1: resolve the place

curl -sf -X POST https://emem.dev/v1/locate \
  -H 'content-type: application/json' \
  -d '{"q":"Bengaluru, India"}' \
  | jq '{cell64, place_label, via, disambiguation_required}'

place is accepted as a synonym of q, and {"lat":..,"lng":..} skips the geocoder. When disambiguation_required is true, or selected.is_high_confidence is false, read alternatives and ask the user which one they meant rather than citing rank 0. "Springfield" returns Missouri first and flags it; that is the case this exists for.

Step 2: recall the bands

CELL=defi.zb493.zezo.zcb35
curl -sf -X POST https://emem.dev/v1/recall \
  -H 'content-type: application/json' \
  -d "{\"cell\":\"$CELL\",\"bands\":[\"weather.temperature_2m\",\"indices.ndvi\"]}" \
  > recall.json

# The latest reading per band, with the token to cite it by.
jq -r '.current_by_band | to_entries[] | .value' recall.json | while read cid; do
  jq -c --arg c "$cid" '.facts[] | select(.fact_cid == $c)
        | {band, value_verbatim, unit, observed_at, memory_token}' recall.json
done