managing-shared-memory SKILL.md skillA
managing-shared-memory from letta-ai/letta-code is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add letta-ai/letta-code/managing-shared-memory@git:20261030.9d1220bPins git:20261030.9d1220b in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- letta-ai/letta-code
- Path
src/skills/builtin/managing-shared-memory/SKILL.md- Versions recorded
- 4
- Latest version
- git:20261030.9d1220b, committed Oct 30, 2026
- First version recorded
- Jul 28, 2026
- Size
- 7,837 bytes
- Repository stars
- 3,790
- License
- Apache-2.0
Create and manage shared memory — git-tracked repositories hosted on Letta Cloud that are attached to one or more agents and projected into their filesystems. Use when the user wants to share memory or files across agents, store context outside your own MemFS, attach or detach shared memory, or inspect its file history.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Managing Shared Memory Shared memory is memory created independently of any single agent, designed to be dynamically attached to or detached from multiple agents. Each unit of shared memory is a **shared memory repository**: a git repository hosted on Letta Cloud, owned by your organization rather than by one agent, reachable from any environment (sandboxes, remote machines, sessions). Shared memory works like your MemFS: attached repositories are real git checkouts on disk, and you read, edit, and commit with ordinary git. The harness pushes clean committed changes after each turn. Each repository has its own projection root (next to your memory directory, not inside it) and its own remote origin, and other agents may be writing to it too. Create a shared memory repository when: - You have context an agent should be able to access that doesn't belong in its own MemFS (input files, datasets, docs, working artifacts) - Multiple agents need to read or write the same context - You want a versioned file store that survives across environments and sessions ## Working with Files (the normal path) …
Read the whole file at its exact version.
How to install
mdr add letta-ai/letta-code/managing-shared-memory@sha256:82b07b6b183e6b0cThe line at the top of this page pins the label git:20261030.9d1220b, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_j3rk4e7lyek6z2gd)
7 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Jul 28, 2026 and Oct 30, 2026, about one every 31 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261030.9d1220b latest | 2026-10-30 | 9d1220b | 7,837 B | A | view · diff |
| git:20260828.c9c32a1 | 2026-08-28 | c9c32a1 | 5,621 B | A | view · diff |
| git:20260804.2f19066 | 2026-08-04 | 2f19066 | 5,453 B | A | view · diff |
| git:20260728.e784581 | 2026-07-28 | e784581 | 6,278 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (7837 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
letta-ai/letta-code · 3,790 stars · license Apache-2.0 · pushed 2026-11-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_j3rk4e7lyek6z2gd GET https://markdownregistry.com/api/v1/resolve?ref=letta-ai/letta-code/managing-shared-memory GET https://markdownregistry.com/api/v1/blob/82b07b6b183e6b0c2cec1233aab4019b6a93e1dc5830ec0615d8768b9290b118
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.