Connect Cursor

Cursor knows the repo. It does not know the exception in the browser, the doc you read at lunch, or what the team decided on the call. The official skills give it that surrounding context.

The skills live in the official repo: Memories-ai-labs/Luci-skills.

Install the skills

From LUCI

1. Turn on screen memory and leave LUCI running.
2. Open Settings → Agent access.
3. Tick Cursor and click Install.

LUCI writes luci and distill into ~/.cursor/skills/.

From GitHub

npx skills add Memories-ai-labs/Luci-skills

Or install globally, for every project:

npx skills add Memories-ai-labs/Luci-skills -g

You can also paste this into Cursor:

Install this agent skill for me: https://github.com/Memories-ai-labs/Luci-skills

Try asking

• "Search my screen memory for the TypeError I saw in the browser console"
• "What was on my screen when the deploy failed?"
• "Find where we discussed the schema change in today's call"
• "distill my life"

Optional: connect over MCP

If you would rather give Cursor the tools without the skills, add the ready-made Cursor snippet from LUCI's Screen Memory panel to ~/.cursor/mcp.json (or a project-level .cursor/mcp.json). Confirm "luci" appears in Cursor's connections. The same snippet is on the Cursor integration page.

Skills are the recommended path. MCP is the fallback.

Notes

• This is not Cursor's own editor memory. LUCI covers everything outside the repo, and the same skills work in Claude Code and Codex.
• What Cursor pulls becomes part of that conversation. See Agent Bridge.