agentleFS
matrixoriginmatrixorigin/Memoria/skills/setup/SKILL.md

setup

Skill624 starsChanged 6 months agoApache-2.0View on GitHub

Install Memoria and configure MCP for AI tools (Kiro, Cursor, Claude Code, Codex, Gemini CLI). Decision tree for Cloud vs self-hosted mode, database, embedding provider. Use when helping users set up Memoria.

  • Pipes a download into a shell
  • Reads credentials

191 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use add-voice-transcription, add-discord and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • juancruzmunozalbeloSkill

    add-voice-transcription

    Add voice message transcription to NanoClaw using OpenAI's Whisper API. Automatically transcribes WhatsApp voice notes so the agent can read and respond to them.

    Also in 5 projects that use this

  • MicrosoftSkill

    add-discord

    Add Discord bot channel integration via Chat SDK.

    Also in 11 projects that use this

  • MicrosoftSkill

    add-slack

    Add Slack channel integration via Chat SDK.

    Also in 11 projects that use this

  • juancruzmunozalbeloSkill

    add-telegram-swarm

    Add Agent Swarm (Teams) support to Telegram. Each subagent gets its own bot identity in the group. Requires Telegram channel to be set up first (use /add-telegram). Triggers on "agent swarm", "agent teams telegram", "telegram swarm", "bot pool".

    Also in 7 projects that use this

  • +8 more from microsoft

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 4 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 170 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Follow these steps in order.

    line 8
  2. Very specific:

    Ask: "Use Memoria Cloud, or run your own instance?"

    line 12
  3. Distinctive:

    Ask: "Which AI tool are you using — Kiro, Cursor, Claude Code, Codex, or Gemini CLI?"

    line 19
  4. Distinctive:

    Ask: "Do you have a MatrixOne database running?"

    line 35
  5. Distinctive:

    Ask: "Do you have an OpenAI-compatible embedding endpoint?"

    line 46
  6. Very specific:

    After running memoria init, tell user to:

    line 128
  7. Distinctive:

    Ask the AI: *"Do you have memory tools available?"*

    line 131

“Common” is measured: kept by at least 6 in 10 of the 170 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Decision Tree

Follow these steps in order. Steps marked "Self-Hosted only" can be skipped for Memoria Cloud users.

Step 1: Memoria Cloud or Self-Hosted?

Ask: "Use Memoria Cloud, or run your own instance?"

  • Memoria Cloud (recommended) → sign up at thememoria.ai, get API URL + token, then proceed to Step 2
  • Self-hosted → proceed to Step 2

Step 2: Which AI tool?

Ask: "Which AI tool are you using — Kiro, Cursor, Claude Code, Codex, or Gemini CLI?"

The --tool flag value and config files generated per tool:

Tool--tool valueConfig files
Kirokiro.kiro/settings/mcp.json + .kiro/steering/memory.md
Cursorcursor.cursor/mcp.json + .cursor/rules/memory.mdc
Claude Codeclaude.mcp.json + CLAUDE.md
Codexcodex~/.codex/config.toml + AGENTS.md
Gemini CLIgemini.gemini/settings.json + GEMINI.md

Step 3: Database (Self-Hosted only)

Skip this step if user chose Memoria Cloud in Step 1.

Ask: "Do you have a MatrixOne database running?"

  • Already have one → get connection URL (format: mysql+pymysql://<user>:<pass>@<host>:<port>/<db>)
  • No → run docker compose up -d in the Memoria repo root (wait 30-60s for first start)

Step 4: Embedding provider (Self-Hosted only)

Skip this step if user chose Memoria Cloud in Step 1.

⚠️ Hard to reverse. Embedding dimension is locked into schema on first startup.

Ask: "Do you have an OpenAI-compatible embedding endpoint?"

  • Yes → collect: base URL, API key, model, dimension
  • No → suggest SiliconFlow (free tier) or Ollama. Local embedding requires --features local-embedding build.

Step 5: Install Memoria CLI

The memoria binary is required for all modes — it serves as the MCP bridge between the AI tool and the Memoria server.

One-line install (recommended):

curl -sSL https://raw.githubusercontent.com/matrixorigin/Memoria/main/scripts/install.sh | bash

Or download manually from GitHub Releases.

Platform-specific manual install:

# Linux x86_64
curl -LO https://github.com/matrixorigin/Memoria/releases/latest/download/memoria-x86_64-unknown-linux-musl.tar.gz
tar xzf memoria-x86_64-unknown-linux-musl.tar.gz && sudo mv memoria /usr/local/bin/

# macOS Apple Silicon
curl -LO https://github.com/matrixorigin/Memoria/releases/latest/download/memoria-aarch64-apple-darwin.tar.gz
tar xzf memoria-aarch64-apple-darwin.tar.gz && sudo mv memoria /usr/local/bin/

# From source (required for local embedding)
cd Memoria/memoria && cargo build --release -p memoria-cli
# With local embedding: cargo build --release -p memoria-cli --features local-embedding
sudo cp target/release/memoria /usr/local/bin/

Verify: memoria --version

Step 6: Configure

Memoria Cloud (Remote Mode)

Sign up at thememoria.ai — after login you will receive the API URL and token.

cd <user-project>
memoria init --tool <tool> --api-url '<API URL from thememoria.ai>' --token '<your token>'

Replace <tool> with the value from Step 2 (e.g., kiro, cursor, claude, codex, gemini).

Self-Hosted: Local Docker

docker compose up -d                    # Start MatrixOne
docker ps --filter name=matrixone       # Verify (wait 30-60s)
cd <user-project>
memoria init --tool <tool>              # + embedding flags below

Self-Hosted: Existing DB

cd <user-project>
memoria init --tool <tool> --db-url 'mysql+pymysql://<user>:<pass>@<host>:<port>/<db>'

Embedding Flags (Self-Hosted only)

# Local (default, no flags)
memoria init --tool <tool>

# OpenAI-compatible
memoria init --tool <tool> \
  --embedding-provider openai \
  --embedding-base-url https://api.siliconflow.cn/v1 \
  --embedding-api-key sk-... \
  --embedding-model BAAI/bge-m3 \
  --embedding-dim 1024

Step 7: Verify

After running memoria init, tell user to:

  1. Restart their AI tool
  2. Ask the AI: "Do you have memory tools available?"
  3. Or run: memoria status

Expected: memory_retrieve("test") → "No relevant memories found".

Post-Setup

memoria rules --force   # After upgrading Memoria binary, re-sync steering rules

MCP Server Modes (Reference)

These are the underlying commands that memoria init configures. Users normally don't need to run them directly.

# Embedded mode (direct DB connection, self-hosted)
memoria mcp --db-url "mysql+pymysql://root:111@localhost:6001/memoria" --user alice

# Remote mode (proxy to Memoria API server, Cloud or self-hosted API)
memoria mcp --api-url "<API URL>" --token "<token>"

# SSE transport (alternative to default stdio)
memoria mcp --transport sse

Troubleshooting

ProblemFix
MatrixOne won't startdocker logs memoria-matrixone
Port 6001 in useChange MO_PORT in .env
Can't connect to DBWait 30-60s on first start
Docker permission deniedsudo usermod -aG docker $USER && newgrp docker
Docker not availableUse Memoria Cloud instead (no Docker needed)
First query slowNormal with local embedding (~3-5s). Use openai provider for faster response
local-embedding not compiledUse OpenAI-compatible service, or build from source with --features local-embedding
AI tool doesn't see memory tools1. Run which memoria to verify CLI installed 2. Restart AI tool 3. Test MCP server directly

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.