Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Search, summarize, and extract insights from your Limitless AI pendant life logs. Supports keyword and semantic search, date range queries, memory recall, an...
Search, summarize, and extract insights from your Limitless AI pendant life logs. Supports keyword and semantic search, date range queries, memory recall, an...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
You have access to the user's Limitless AI pendant recordings via the Limitless REST API. Use the tools below to retrieve, search, and analyze life log transcriptions.
Read these values from the environment before any API call: VariableRequiredDescriptionLIMITLESS_API_KEYYesAPI key from Limitless Developer settingsLIMITLESS_TIMEZONENoIANA timezone (e.g. America/Los_Angeles). Defaults to UTC If LIMITLESS_API_KEY is not set, stop and tell the user: "Please set your API key first: export LIMITLESS_API_KEY=your_key_here" If LIMITLESS_TIMEZONE is not set, proceed with UTC and note it in your response.
Base URL: https://api.limitless.ai Auth header: X-API-Key: $LIMITLESS_API_KEY This skill is READ-ONLY โ never call DELETE endpoints.
curl -s -H "X-API-Key: $LIMITLESS_API_KEY" \ "https://api.limitless.ai/v1/lifelogs?timezone=$LIMITLESS_TIMEZONE&PARAMS" Query parameters (append as &key=value): ParamTypeDescriptionqstringHybrid semantic + keyword search querydateISO-8601 dateFilter to a specific day (YYYY-MM-DD)startISO-8601 datetimeRange startendISO-8601 datetimeRange endlimitintegerResults per page (default 10, max 50)cursorstringPagination cursor from previous nextCursordirectionasc|descSort order (default desc)includeMarkdownbooleanInclude formatted markdown contentincludeHeadingsbooleanInclude section headings
curl -s -H "X-API-Key: $LIMITLESS_API_KEY" \ "https://api.limitless.ai/v1/lifelogs/LOG_ID"
If the response includes "nextCursor" in the meta object, fetch the next page by appending &cursor=NEXT_CURSOR to the same request. Continue until nextCursor is null or you have enough data.
Trigger phrases: "search my logs for...", "find mentions of...", "did anyone say..." Extract the search term from the user's message. Call the lifelogs endpoint with q=<term> and limit=10. Present results as a numbered list: timestamp, a short excerpt, and the log ID. Offer to fetch more pages or open a specific log.
Trigger phrases: "what happened today", "summarize this week", "recap yesterday" Determine the date or range from the user's intent. "today" โ date=<today's date> "this week" โ start=<Monday>&end=<today> "yesterday" โ date=<yesterday> Fetch up to 50 logs for the range (paginate if needed). Synthesize a structured summary: Key topics and conversations Decisions made People mentioned Notable moments
Trigger phrases: "what did we decide about...", "who mentioned...", "remind me about..." Identify the topic or entity from the user's question. Search with q=<topic>, fetching enough results to answer. Synthesize a direct answer citing the relevant log entries (include date and time).
Trigger phrases: "show me logs from...", "what was recorded on...", "logs between X and Y" Parse the date or range from the user's message. Fetch logs with date= or start=/end=. Present a chronological list with titles, timestamps, and brief summaries.
Trigger phrases: "extract tasks", "what did I ask [agent] to do", "find action items for...", or automatically after fetching logs when the user asks for a recap. Agent Roster Load the configured agents from the roster file and extract the list of known agent names: cat ~/.openclaw/workspace/skills/limitless/agents.json | jq '[.agents[].name]' Use these names as the detection vocabulary. Never hardcode agent names in logic โ always derive them from agents.json at runtime. Detection Rules Scan the lifelog transcription text for directives to any agent in the roster. An action item is present when: A known agent name (from the roster) appears as a direct address at the start of a phrase or sentence Examples: "<AgentName>, send...", "Hey <AgentName> can you...", "@<AgentName> please...", "<AgentName> โ I need you to..." A task verb follows: send, schedule, remind, book, find, create, draft, write, check, follow up, research, compile, etc. The phrase contains a clear deliverable or target Extraction Format For each detected action item, output: Agent: <agent name> Trigger: "<exact quote from transcript>" Task: <one-sentence plain-English summary of what was asked> From log: <log ID> โ <timestamp> Dispatch Prompt After presenting each extracted action item, ask the user: "Should I dispatch this task to [Agent Name]?" If the user says yes, read the agent's dispatch config from agents.json and use the appropriate method: webhook: POST to dispatch.url with JSON body: { "agent": "<name>", "task": "<task summary>", "source_quote": "<exact quote>", "log_id": "<log ID>", "timestamp": "<ISO timestamp>" } curl -s -X POST -H "Content-Type: application/json" \ -d '{"agent":"NAME","task":"TASK","source_quote":"QUOTE","log_id":"ID","timestamp":"TS"}' \ "DISPATCH_URL" email: Inform the user what the email should contain and ask them to send it, or use the system mail command if available: echo "Task for AGENT_NAME:\nTASK_SUMMARY\n\nSource: QUOTE\nLog: LOG_ID" | \ mail -s "Task from Limitless" AGENT_EMAIL If the agent name is not in the roster, flag it: "I found a task directed at '[Name]' but they're not in your agents.json roster. Add them to ~/.openclaw/workspace/skills/limitless/agents.json to enable dispatch."
SituationResponseLIMITLESS_API_KEY not setStop and prompt user to export itHTTP 401"Your API key appears invalid. Check it in Limitless Developer settings."HTTP 429"Rate limit hit (180 req/min). Wait 60 seconds and try again."HTTP 404"That log ID wasn't found. It may have been deleted or the ID is incorrect."Empty results"No logs found matching that query. Try a broader search term or different date range."agents.json missing"agents.json not found. Create it at ~/.openclaw/workspace/skills/limitless/agents.json using the template in the skill repo."
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.