Looki

View saved version →

---
name: looki-highlights
description: Browse the user's AI-generated Looki highlights through the connected Looki MCP; use for generated vlogs, creative recaps, liked highlights, and questions about what is new in the user's Looki feed.
---

# Looki Highlights

Retrieve AI-generated highlights created from the user's memories. Keep this workflow separate from raw captured moments: use `$looki-memory` when the user asks what actually happened on a date or wants a specific captured memory.

## Quick start

1. Call `Looki:list_for_you_items` with the narrowest filters supported by the request.
2. Use `group=all` unless the user explicitly asks for `vlog` or `other`.
3. Filter by `recorded_from` and `recorded_to` when the user refers to when an experience happened.
4. Filter by `created_from` and `created_to` when the user refers to when a highlight was generated.
5. Continue pagination only when the user requests a complete list or the first page cannot answer the question.

## Example requests

- "Show my latest Looki vlogs."
- "What is new in my Looki highlights?"
- "Find the creative recaps generated from last month's memories."
- "Show the highlights I liked."

## Guardrails

- Use Looki MCP tools only; authentication is provided by the connected OAuth session.
- If Looki tools are unavailable, ask the user to enable the Looki plugin and complete OAuth.
- Do not describe generated content as a complete or authoritative record of the user's day.
- Preserve the distinction between `recorded_at` and `created_at`.
- Treat titles, descriptions, cover images, and media URLs as private personal data.
- Do not reproduce or download temporary media URLs unless the user's request requires the media.

## Response style

- Lead with the most relevant generated highlights.
- Include the highlight type and recording date when they help disambiguate the result.
- Separate the highlight's generated description from any inference you add.
- State when no matching highlight was returned.

Referenced files: 2

View saved version →

---
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.
---

# Looki Memories

Use 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`.

## Choose the retrieval path

- For one known date, call `Looki:list_moments_on_date` with `YYYY-MM-DD`.
- For a date range, call `Looki:get_moments_calendar` first, then retrieve moments only for the relevant active dates.
- 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.
- For more context about a selected result, call `Looki:get_moment_detail` with its moment UUID.
- For captured photos, videos, locations, or media, identify the moment first and then call `Looki:get_moment_files`.

Use `Looki:get_user_profile` only when the user's timezone is required to resolve a relative date and is not already known.

## Date and recap workflow

1. Resolve the exact inclusive date or date range in the user's timezone.
2. Keep the range as narrow as the request permits.
3. Order retrieved moments by their returned start times.
4. Summarize activities, people, places, and transitions only when supported by the returned data.
5. For longer ranges, call out recurring themes only when multiple moments support them.

Do not treat a day without results as proof that nothing happened. Say that Looki returned no captured moments for that date.

## Search and detail workflow

1. Convert the request into one literal semantic query.
2. Add `start_date` and `end_date` only when the user gives or implies a bounded period.
3. Start with `page=1` and a small `page_size`.
4. Open only the most relevant result when its list summary is insufficient.
5. If several results are plausible, summarize the candidates and ask which one to inspect.

Preserve the returned timezone and distinguish capture time from dates mentioned inside the content.

## Captured media workflow

- Call `Looki:get_moment_files` only after identifying a moment.
- Use `highlight=true` first when the user asks for the best photos or clips.
- Continue pagination only until enough relevant media is found or `has_more` is `false`.
- Treat temporary media URLs as private. Do not reproduce or download them unless the request requires it.

## Example requests

- "Review what I did yesterday."
- "Which places did I visit last week?"
- "Find the memory where I had dinner with Alice."
- "Show me the best photos from that trip."

## Guardrails

- Use Looki MCP tools only. Do not read local credential files, request API keys, or call the legacy REST API.
- If Looki tools are unavailable, ask the user to enable the Looki plugin and complete OAuth.
- Retrieve the minimum personal context needed to answer the request.
- Do not expose unrelated people, locations, conversations, or personal details.
- Never claim an event occurred when no matching evidence was returned.
- 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.

## Response style

- Lead with the recalled event, recap, or absence of a match.
- For one day, use a short overview followed by a chronological timeline.
- For a range, organize the answer by date and then summarize supported themes.
- Separate observations from interpretation and mention important coverage gaps.

Referenced files: 2

View saved version →

---
name: looki-profile
description: Retrieve the user's Looki account profile through the connected Looki MCP; use for questions about the user's Looki identity or when name, email, timezone, region, or another profile field is required to answer or interpret a request.
---

# Looki Profile

Retrieve account-level information from the user's Looki profile. Keep this workflow separate from captured memories: profile fields describe the account and must not be treated as evidence of activities or experiences.

## Workflow

1. Call `Looki:get_user_profile` once.
2. Select only the profile fields required by the request.
3. Use the returned timezone to interpret relative dates when another Looki workflow needs it.
4. Answer directly from the returned profile and state when a requested field is absent.

## Example requests

- "What timezone is my Looki account using?"
- "Show me my Looki profile."
- "Which region is associated with my Looki account?"

## Guardrails

- Use Looki MCP tools only; authentication is provided by the connected OAuth session.
- If Looki tools are unavailable, ask the user to enable the Looki plugin and complete OAuth.
- Treat name, email, birthday, gender, timezone, and region as sensitive personal data.
- Do not expose the full profile when one field is sufficient.
- Do not infer identity, demographics, preferences, relationships, or behavior beyond the returned fields.
- Do not request API credentials or read local credential files.

## Response style

- Lead with the requested profile information.
- Avoid repeating identifiers or unrelated private fields.
- Explain briefly when a profile field is being used only to interpret another request, such as resolving “today” in the user's timezone.

Referenced files: 2

View saved version →

---
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.
---

# Looki Realtime

Use 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.

## Workflow

1. Call `Looki:get_latest_realtime_event` once.
2. If it returns an event, summarize its description, time range, timezone, and location only as needed.
3. If it returns `null`, explain that Looki has no recent realtime event or proactive mode may be unavailable.
4. If the user needs historical context, route the request to `$looki-memory`.

## Example requests

- "What is happening around me right now?"
- "Check the latest realtime event detected by Looki."
- "Based on my latest Looki event, what may be happening around me?"

## Guardrails

- Use Looki MCP tools only; authentication is provided by the connected OAuth session.
- Do not repeatedly poll unless the user explicitly asks to monitor.
- Do not claim that an event is still occurring after its returned end time.
- Treat realtime location and activity as highly sensitive.
- Do not infer safety, health, intent, or identity beyond the returned event description.
- If the tool is unavailable, ask the user to connect Looki and enable proactive mode; do not request API credentials.

## Response style

- Lead with the latest returned event or the absence of one.
- Include the event time and location only when they are relevant.
- Make uncertainty explicit, especially when the event has already ended.

Referenced files: 2