← LookiCONTENT HISTORYWHAT CHANGED · RULE-BASED ANALYSIS
Update to Looki
Snapshot Sep 30, 2026 · 23:01 UTC · version 1.0.0
Collection source: not recorded for this historical snapshot.
First saved snapshot
No earlier snapshot is available to establish a change.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"name": "looki-realtime",
"description": "Check the latest realtime event detected by the user's Looki device through the connected Looki MCP; use when the user asks what is happening now or requests immediate context from proactive mode.",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 309
},
{
"relative_path": "assets/icon.png",
"size_in_bytes": 4506
}
],
"skill_md_contents": "---\nname: looki-realtime\ndescription: Check the latest realtime event detected by the user's Looki device through the connected Looki MCP; use when the user asks what is happening now or requests immediate context from proactive mode.\n---\n\n# Looki Realtime\n\nUse the latest realtime Looki event only for explicit current-context requests. This capability is beta and depends on proactive mode being enabled in the Looki app.\n\n## Workflow\n\n1. Call `Looki:get_latest_realtime_event` once.\n2. If it returns an event, summarize its description, time range, timezone, and location only as needed.\n3. If it returns `null`, explain that Looki has no recent realtime event or proactive mode may be unavailable.\n4. If the user needs historical context, route the request to `$looki-memory`.\n\n## Example requests\n\n- \"What is happening around me right now?\"\n- \"Check the latest realtime event detected by Looki.\"\n- \"Based on my latest Looki event, what may be happening around me?\"\n\n## Guardrails\n\n- Use Looki MCP tools only; authentication is provided by the connected OAuth session.\n- Do not repeatedly poll unless the user explicitly asks to monitor.\n- Do not claim that an event is still occurring after its returned end time.\n- Treat realtime location and activity as highly sensitive.\n- Do not infer safety, health, intent, or identity beyond the returned event description.\n- If the tool is unavailable, ask the user to connect Looki and enable proactive mode; do not request API credentials.\n\n## Response style\n\n- Lead with the latest returned event or the absence of one.\n- Include the event time and location only when they are relevant.\n- Make uncertainty explicit, especially when the event has already ended.\n"
}SHA-256: e7be6a2bb06d3106dbae9a22e0fdf919c3f4eb863318ad99707d0198cdca76ff