Connect Goose

Goose can run your shell, edit files, and call whatever tools you hand it. It still starts every session with no idea what you read this morning or what got decided on the last call. The official LUCI skills teach it when to look that up, 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 write into Goose, so install from the repo.

From your project folder:

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

That writes into the project's .goose/skills/. To install for every project:

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

The global install goes to ~/.config/goose/skills/, which Goose reads on Mac and Linux. Goose on Windows keeps its config under %APPDATA%, so use the project install there.

Or ask Goose:

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

That puts luci and distill on the agent. Goose reads skills when a session starts, so open a new session, then run goose skills list to check they are there.

Already installed the skills into Claude Code from LUCI? Goose also reads ~/.claude/skills/, so a new Goose session has them with nothing else to do. This works on Windows too.

Try asking

• "What was I looking at before lunch?"
• "Find the stack trace I saw in the terminal this morning"
• "What did we decide about the release date on today's call?"
• "distill my life"

To load a skill by name in the Goose CLI, type /skills luci.

Optional: connect over MCP

If you would rather give Goose the tools without the skills, add LUCI as a remote extension. LUCI has no Goose preset, so copy the URL and token from Settings → Agent access → Manual MCP setup in LUCI. Then add this to ~/.config/goose/config.yaml (on Windows, %APPDATA%\Block\goose\config\config.yaml):

extensions:
  luci:
    type: streamable_http
    name: luci
    enabled: true
    uri: "<url>"
    headers:
      Authorization: "Bearer <token>"
    timeout: 300

If the file already has an extensions: key, put the luci entry under it rather than adding a second one. Restart Goose afterwards. A session that is already open does not see config file edits.

More on the protocol path: Connect over MCP.

Skills are the recommended path. MCP is the fallback.

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