SkillFoxx

Memori skill

A Claude Code skill that pulls memory from Memori Cloud before every non-trivial answer and writes new facts back to it

  • 17,556 ★ on the repository
  • Last commit
Skill

Extended access

Why this level

  • It sends dialogue facts and context to the Memori Cloud store
All reasons and checks

memorilabs/memoriAuthor:MemoriLabs

Install

In your terminal, with SkillFoxx CLI

npx skillfoxx add skills/memori

Detects the agents on your machine, shows the access level and pins the version.

Other ways to install

Access and checks

How we review

Extended accessThe tool runs code or makes network calls and only reads external data.

  • It sends dialogue facts and context to the Memori Cloud store

This is third-party code. Review the repository files before installing.

What it does

The memori skill wraps Memori Cloud in a thin CLI call for Claude Code and runs ambiently: before answering a non-trivial question, the agent reaches into memory for relevant context on its own, without waiting to be asked to 'remember'. After answering, it writes new facts and decisions back so they carry over into future sessions and other projects for the same user. Besides the Claude Code skill, Memori has TypeScript and Python SDKs, an MCP integration and an OpenClaw plugin, all talking to the same cloud memory store.

Who it is for. For developers who want Claude Code to remember project decisions and context across sessions without manually re-explaining them.

Good fit when

  • You need the agent to remember preferences and past decisions without being reminded
  • Work on a project spans a long time and context accumulates session by session
  • You need one memory shared across several integrations: Claude Code, MCP, OpenClaw

Not a fit when

  • The project is one-off and there is no reason to persist context between sessions
  • You cannot set up a Memori Cloud account and API key

Example request

Use Memori to recall which architecture decision we made for this module last time

Limitations

The skill is a thin client to Memori Cloud, so it needs a cloud API key and a stable user identifier. Self-hosting is possible via the open Rust core with Node and Python bindings, but it requires a separate database infrastructure.

How to disable. Remove the memori folder from .claude/skills, or remove MEMORI_API_KEY from .claude/settings.local.json so the skill stops being invoked.

FAQ

Do I need to explicitly ask the agent to remember something?

No, the skill is described as triggering on almost every non-trivial turn; the agent checks memory before answering on its own.

Can it be used outside Claude Code?

Yes, there are TypeScript and Python SDKs, an MCP skill and an OpenClaw plugin on top of the same cloud store.

Discussion

No questions or reviews yet.

Skills

Shared local memory for AI agents: Claude Code, Codex, Cursor and others find the agreements of past sessions in it and record new ones

CLIBroad access2.2K
Official

MemoMind MCP gives Claude Code project memory, with stored facts, events and conclusions visible in a local dashboard.

MCP serverExtended access603
Editors’ pick

Memory layer for agents: plugins for Claude Code, Codex, Cursor and OpenCode, plus a CLI and SDKs that carry context across sessions

PluginExtended access68.9K

Local memory for Claude Code, Codex and Claude Desktop: one Markdown folder and one MCP server shared by all.

MCP serverExtended access103
Official

Long-term memory for agents: a remote MCP server, plugins for Claude Code, Cursor and Codex, and an API for your own apps

MCP serverExtended access31.6K

A local workbench for Claude Code, Codex, Pi and OpenCode: memory changes wait for your review, then an audit follows each turn

CLIExtended access279

README in short

The README describes Memori as LLM- and datastore-agnostic agent memory infrastructure that turns agent execution and conversation into structured, persistent state. It shows SDK installs via npm and pip and a quick start through Memori Cloud with a single API key. The repo includes integrations: a SKILL.md for Claude Code, an MCP skill in the cloud docs, and an OpenClaw plugin with two skills.

README badge

Original SKILL.md

---
name: memori
description: >
  Ambient Memori long-term memory for Claude Code via local Bash. MUST TRIGGER
  on essentially every non-trivial user turn: run recall before drafting any
  substantive response, whether or not the user mentioned memory, a prior
  session, or past work. The default is to check memory first; do not wait to
  be asked. Always fire before external lookups (WebSearch/WebFetch) and
  before answering any question about preferences, prior decisions,
  constraints, project history, status, past work, or any non-trivial
  coding/research task. Skip only for trivial acknowledgements/closings,
  purely self-contained turns where prior context cannot possibly help, or
  when the user explicitly opts out.
argument-hint: '<command> [--flags ...]'
allowed-tools: Bash
---

# Memori Claude Code Skill

Thin CLI wrapper around Memori Cloud for Claude Code subprocesses. Memori is an
ambient memory enhancement, not an explicit destination tool. Do not wait for
the user to ask to "use Memori" before applying the memory lifecycle below.

Report a problem