메뉴
Use when recalling conversations from Limitless Pendant, finding what was discussed in meetings, searching lifelogs, or answering 'what did I say about' questions
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | limitless |
| description | Use when recalling conversations from Limitless Pendant, finding what was discussed in meetings, searching lifelogs, or answering 'what did I say about' questions |
| version | 1.0.0 |
| category | research |
| triggers | ["limitless","pendant","lifelogs","what did I say","what was discussed","conversation history","ambient recording"] |
Clear triggers:
Optional: Set LIMITLESS_TIMEZONE (defaults to America/Chicago).
limitless today
limitless date 2026-01-28
limitless search "meeting with john" limitless search "restaurant recommendation"
limitless raw "limit=5&isStarred=true"
</commands>
<response-format>
Lifelogs include:
- **title** - AI-generated summary
- **markdown** - Full transcript with timestamps
- **startTime/endTime** - When recorded
- **contents** - Structured segments with speaker attribution
Speaker names show as "Unknown" unless voice profiles are trained in the Limitless app.
</response-format>
<api-notes>
- Rate limit: 180 requests/minute
- Requires Limitless Pendant hardware
- Developer portal: [limitless.ai/developers](https://www.limitless.ai/developers)
- API examples: [github.com/limitless-ai-inc/limitless-api-examples](https://github.com/limitless-ai-inc/limitless-api-examples)
</api-notes>
<llm-api-reference>
If you need to look up API details beyond this skill's commands, use Context7:
resolve-library-id: limitless → /websites/help_limitless_ai_en query-docs: /websites/help_limitless_ai_en with "lifelogs API" query
Or fetch current docs directly from https://www.limitless.ai/developers
</llm-api-reference>
Use when facing hard architectural decisions, multiple valid approaches exist, need diverse perspectives before committing, or want M-of-N synthesis on complex problems
Use when rough ideas need design before code, requirements are fuzzy, multiple approaches exist, or you need to explore options before implementation
Use when testing MCP servers, debugging MCP tool responses, exploring MCP capabilities, or diagnosing why an MCP tool returns unexpected data
Use when debugging bugs, test failures, unexpected behavior, or needing to find root cause before fixing
Use when managing project learnings - view, add, search, prune, or export operational knowledge that persists across sessions
Use when shipping code - complete workflow: merge main, run tests, multi-review with auto-fix, commit, push, create PR. Replaces manual commit-push-pr flows.