Connect Kiro

Kiro works from your specs and the repo. Neither one holds the error you saw in the browser or the decision from this morning's call. The official LUCI skills teach Kiro when to search your memory and how to distill your day.

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

Install the skills

LUCI's in-app installer does not list Kiro, so install from the repo.

npx skills add Memories-ai-labs/Luci-skills -g -a kiro-cli

The installer calls the target "Kiro CLI", but the folder it writes, ~/.kiro/skills/, is the global skills folder for both the Kiro IDE and Kiro CLI. Drop -g to install into this project's .kiro/skills/ instead.

That puts luci and distill on the agent.

From the Kiro IDE

Open the Kiro panel, go to Agent Steering & Skills, click +, choose Import a skill, then GitHub. Kiro imports one skill folder at a time, not a whole repo, so paste each URL separately:

https://github.com/Memories-ai-labs/Luci-skills/tree/main/skills/official/luci
https://github.com/Memories-ai-labs/Luci-skills/tree/main/skills/official/distill-my-life

Try asking

• "What was I looking at before I opened this spec?"
• "Find the error I saw in the browser this morning"
• "What did we decide about the API on yesterday's call?"
• "distill my life"

You can also type /luci or /distill-my-life in Kiro's chat.

Optional: connect over MCP

If you would rather give Kiro the tools without the skills, copy the URL and token from Settings → Agent access → Manual MCP setup in LUCI into ~/.kiro/settings/mcp.json (every workspace) or .kiro/settings/mcp.json (one workspace):

{
  "mcpServers": {
    "luci": {
      "url": "<url>",
      "headers": { "Authorization": "Bearer <token>" }
    }
  }
}

Kiro applies the change when you save the file. No restart. In the Kiro IDE, MCP support has to be on. Search Settings for "MCP" and enable it. Kiro asks for https on remote servers but accepts plain http for local ones, and LUCI's server is local.

Skills are the recommended path. MCP is the fallback. More on the protocol path: Connect over MCP.

If Kiro still cannot see your memory, check Common issues. Privacy note: Agent Bridge.