Update to Looki

{
  "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.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 298
    },
    {
      "relative_path": "assets/icon.png",
      "size_in_bytes": 4506
    }
  ],
  "skill_md_contents": "---\nname: looki-profile\ndescription: 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.\n---\n\n# Looki Profile\n\nRetrieve 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.\n\n## Workflow\n\n1. Call `Looki:get_user_profile` once.\n2. Select only the profile fields required by the request.\n3. Use the returned timezone to interpret relative dates when another Looki workflow needs it.\n4. Answer directly from the returned profile and state when a requested field is absent.\n\n## Example requests\n\n- \"What timezone is my Looki account using?\"\n- \"Show me my Looki profile.\"\n- \"Which region is associated with my Looki account?\"\n\n## Guardrails\n\n- Use Looki MCP tools only; authentication is provided by the connected OAuth session.\n- If Looki tools are unavailable, ask the user to enable the Looki plugin and complete OAuth.\n- Treat name, email, birthday, gender, timezone, and region as sensitive personal data.\n- Do not expose the full profile when one field is sufficient.\n- Do not infer identity, demographics, preferences, relationships, or behavior beyond the returned fields.\n- Do not request API credentials or read local credential files.\n\n## Response style\n\n- Lead with the requested profile information.\n- Avoid repeating identifiers or unrelated private fields.\n- Explain briefly when a profile field is being used only to interpret another request, such as resolving “today” in the user's timezone.\n"
}