Skip to content
Skills Library
AI & agents · Tool integration

setup

/setup

Install and connect memry, the persistent memory for AI coding agents. Use when the user wants to set up memry, asks why memry tools are missing, or wants Claude Code to remember context between sessions.

Repository
memry-cli ↗
Licence
MIT
Last repository change
19.10.2026

Assessment and security

86/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content21 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
4
Deprecation

No signals detected. Repository changed on 19.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Install and connect memry, the persistent memory for AI coding agents. Use when the user wants to set up memry, asks why memry tools are missing, or wants Claude Code to remember context between sessions.

Original author description

Install and connect memry, the persistent memory for AI coding agents. Use when the user wants to set up memry, asks why memry tools are missing, or wants Claude Code to remember context between sessions.

How it works

SKILL.md has no level-two headings · 29 lines, 516 words

SKILL.md preview
---
name: setup
description: Install and connect memry, the persistent memory for AI coding agents. Use when the user wants to set up memry, asks why memry tools are missing, or wants Claude Code to remember context between sessions.
---

# Set up memry

memry stores decisions, bug fixes and discoveries on a memry server and gives them back to the agent at the start of the next session. The `memry` CLI does the setup: it logs the user in and registers memry in each agent they choose. This plugin does not register memry itself, so the agent never ends up with the server twice.

Do not try to diagnose an existing installation, and do not read Claude Code's settings files: they can hold credentials. `memry setup` can be run again at any time, and it repairs a partial or broken setup.

Follow these steps in order and stop at the first one that needs the user.

1. **Check whether the CLI is installed.** Run `command -v memry` (on Windows, `where.exe memry`; in PowerShell, `where` without `.exe` is a different command).
   - If the first path it prints is inside the current project folder, stop: a `memry` from the project would run instead of the installed one (CMD on Windows searches the current folder first, and so does a `PATH` that contains `.`). Tell the user not to run it, and to run the remaining steps from their home folder instead.
   - If it is missing, give the user the install command for their system and wait until they confirm it ran:
     - macOS or Linux with Homebrew: `brew install mrtheroi/tap/memry`
     - Any system with Go: `go install github.com/mrtheroi/memry-cli/cmd/memry@latest`. Go puts the binary in `$(go env GOBIN)` or `$(go env GOPATH)/bin`, which is not on the `PATH` by default; the user must add that folder to their `PATH` and open a new terminal.
     - Otherwise, download a release from https://github.com/mrtheroi/memry-cli/releases and follow https://github.com/mrtheroi/memry-cli#install.
   - Then run the lookup again. Continue only when it finds `memry`.

2. **Log in and connect.** `memry setup` is interactive: it asks for the user's email, sends a 6-digit code and asks which agents to connect. Do not run it yourself. Ask the user whether they set memry up before with a custom config file (`--config`), then ask them to run it in their terminal:
   - memry Cloud: `memry setup`
   - A self-hosted memry server, with a token from their admin: `memry setup --url https://their-memry-server --token`
   - With a custom config file, add the same `--config <path>` they used before, so the repair keeps that file.
   - When setup asks which agents to connect, make sure **Claude Code** is selected. The prompt preselects the agents saved from an earlier setup, which may not include it. Keep any other agents they still use selected.

3. **Start a new session.** Setup registers the `memry` MCP server and a hook that loads the user's memories when a session starts. Both take effect in the next Claude Code session. If memry's tools are still missing afterwards, the user can check `/mcp` for another server named `memry` in the project, and whether hooks are disabled in their settings.

To remove memry later, the user runs `memry uninstall`. `memry delete-account` erases their account and memories. With a custom config file, both need the same `--config <path>`.

More: https://www.memry.com.mx

Versions

RepositoryScoreLicence
This page · mrtheroi/memry-cli86MIT
HwangSlater/harness-fit100MIT
nesquikm/dev-process-toolkit100MIT
userKael/rastro100MIT
als-apg/osprey100BSD-3-Clause
dedujeong/gemba100Apache-2.0
eigenwise/eigenwise-toolshed100MIT
awrshift/agent-memory-kit100MIT
lifecycle-innovations-limited/claude-ops100MIT

Database snapshot: 13.11.2026 · package version 9251432d9249 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100auto-memory
    This skill should be used when the user asks to 'set up memory', 'create memory files', 'create MEMORY.md', 'set up topic files', 'improve memory organization', 'what should I remember', 'how to structure memory files', 'MEMORY.md is too long', 'what goes in memory vs topic…
  • 90setup-agent-md
    Use when a repository needs one canonical instruction file shared by coding agents, when AGENTS.md or CLAUDE.md is missing, or when their guidance has diverged.
  • 90mem9
    Persistent cloud memory for OpenClaw agents. Use when users say: - "install mem9" - "setup memory" - "add memory plugin" - "openclaw memory" - "mem9 onboarding" - "memory not working" - "import memories" - "upload sessions
  • 100agentcairn-setup
    Install, configure, verify, upgrade, or repair AgentCairn persistent cross-agent memory. Use when a user wants shared local-first memory in Claude Code, Codex, Cursor, OpenCode, Antigravity, VS Code, Claude Desktop, or another supported harness; when AgentCairn recall or…
  • 100context-setup
    Install context files from registry. Use when user runs /install-context, says "install context", "setup context", or when context is missing and the user needs to get started.
  • 95cpersona-memory
    Give Claude persistent, searchable memory across sessions using the CPersona MCP server. Use this skill whenever the user wants Claude to remember things between conversations, asks to install or set up CPersona / a memory server, or when CPersona tools are available and the…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.