managing-shared-memory

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.

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

82%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, highly actionable body that assumes Claude's git competence and provides executable commands plus recovery guidance for shared failures. It is concise and clearly navigable, with only minor trimming and structural-split opportunities.

Suggestions

Tighten the opening two paragraphs into a single sentence each to improve conciseness.

Consider moving the SDK/API equivalent note into a short reference section or file so the main flow stays focused on the CLI path.

Add an explicit post-commit verification checkpoint (e.g. confirm the push succeeded or the change appears in history) to strengthen workflow validation.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and assumes git competence; the two opening prose paragraphs and the closing SDK/API note carry useful domain-specific (Letta) context rather than generic concepts, though a little could still be trimmed.	4 / 5
Actionability	Copy-paste-ready commands throughout — `letta shared-memory list/create/attach/detach/sync/history`, `git` operations against `$MEMORY_DIR/../<repo-name>`, and concrete troubleshooting commands covering the common cases.	5 / 5
Workflow Clarity	Clear sequences for create→attach→edit→commit→push and for repair via `sync`, with explicit push-collision recovery (pull --rebase, retry once) and conflict-reminder feedback; minor validation gaps keep it just below a 5.	4 / 5
Progressive Disclosure	Single well-organized SKILL.md with clearly labeled sections (Working with Files, Managing Repositories, Troubleshooting, Notes and Limits); no bundle files exist to reference, and the structure is good though some sub-topics (e.g. the SDK/API paragraph) could be split out.	4 / 5
	Total	17 / 20 Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that concretely states capabilities and provides explicit 'Use when' trigger guidance covering the main use cases. Only minor room to broaden natural-language synonyms.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Create and manage', 'attached... projected into their filesystems', 'share memory or files', 'store context', 'attach or detach', 'inspect its file history' — with comprehensive coverage of the skill's capabilities.	5 / 5
Completeness	Explicitly answers what ('Create and manage shared memory — git-tracked repositories hosted on Letta Cloud...') and when ('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') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Strong natural phrases users would say ('share memory or files across agents', 'attach or detach shared memory', 'inspect its file history'); a few common synonyms or file/extension variants are missing, so it sits just below fully comprehensive.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (Letta Cloud shared memory across agents) with distinct triggers and specific jargon (MemFS, agent attachment) that minimize overlap with unrelated skills.	5 / 5
	Total	19 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: letta-ai/letta-code
Path: src/skills/builtin/managing-shared-memory/SKILL.md
Commit: 7a4337e

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.