Update to Looki

{
  "name": "looki-memory",
  "description": "Retrieve and search the user's captured Looki moments through the connected Looki MCP; use for a specific day or date range, chronological recaps, people, places, topics, past experiences, moment details, and captured photos or videos.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 302
    },
    {
      "relative_path": "assets/icon.png",
      "size_in_bytes": 4506
    }
  ],
  "skill_md_contents": "---\nname: looki-memory\ndescription: Retrieve and search the user's captured Looki moments through the connected Looki MCP; use for a specific day or date range, chronological recaps, people, places, topics, past experiences, moment details, and captured photos or videos.\n---\n\n# Looki Memories\n\nUse captured Looki moments as evidence for questions about the user's past. Route profile-only requests to `$looki-profile`, generated-content requests to `$looki-highlights`, and current-context requests to `$looki-realtime`.\n\n## Choose the retrieval path\n\n- For one known date, call `Looki:list_moments_on_date` with `YYYY-MM-DD`.\n- For a date range, call `Looki:get_moments_calendar` first, then retrieve moments only for the relevant active dates.\n- For a person, place, topic, event, or experience without a known date, call `Looki:search_moments` with one concise natural-language query and optional date bounds.\n- For more context about a selected result, call `Looki:get_moment_detail` with its moment UUID.\n- For captured photos, videos, locations, or media, identify the moment first and then call `Looki:get_moment_files`.\n\nUse `Looki:get_user_profile` only when the user's timezone is required to resolve a relative date and is not already known.\n\n## Date and recap workflow\n\n1. Resolve the exact inclusive date or date range in the user's timezone.\n2. Keep the range as narrow as the request permits.\n3. Order retrieved moments by their returned start times.\n4. Summarize activities, people, places, and transitions only when supported by the returned data.\n5. For longer ranges, call out recurring themes only when multiple moments support them.\n\nDo not treat a day without results as proof that nothing happened. Say that Looki returned no captured moments for that date.\n\n## Search and detail workflow\n\n1. Convert the request into one literal semantic query.\n2. Add `start_date` and `end_date` only when the user gives or implies a bounded period.\n3. Start with `page=1` and a small `page_size`.\n4. Open only the most relevant result when its list summary is insufficient.\n5. If several results are plausible, summarize the candidates and ask which one to inspect.\n\nPreserve the returned timezone and distinguish capture time from dates mentioned inside the content.\n\n## Captured media workflow\n\n- Call `Looki:get_moment_files` only after identifying a moment.\n- Use `highlight=true` first when the user asks for the best photos or clips.\n- Continue pagination only until enough relevant media is found or `has_more` is `false`.\n- Treat temporary media URLs as private. Do not reproduce or download them unless the request requires it.\n\n## Example requests\n\n- \"Review what I did yesterday.\"\n- \"Which places did I visit last week?\"\n- \"Find the memory where I had dinner with Alice.\"\n- \"Show me the best photos from that trip.\"\n\n## Guardrails\n\n- Use Looki MCP tools only. Do not read local credential files, request API keys, or call the legacy REST API.\n- If Looki tools are unavailable, ask the user to enable the Looki plugin and complete OAuth.\n- Retrieve the minimum personal context needed to answer the request.\n- Do not expose unrelated people, locations, conversations, or personal details.\n- Never claim an event occurred when no matching evidence was returned.\n- The current MCP does not expose Looki journals. State that limitation when the user asks for diary or journal entries; do not invent a tool or fall back to the legacy REST API.\n\n## Response style\n\n- Lead with the recalled event, recap, or absence of a match.\n- For one day, use a short overview followed by a chronological timeline.\n- For a range, organize the answer by date and then summarize supported themes.\n- Separate observations from interpretation and mention important coverage gaps.\n"
}