Agent skill · writing content · affaan-m
unified-memory
Share durable, inspectable context and handoffs between Claude, Codex, Hermes, Cursor, OpenCode, and other agents through the local ECC Memory Vault. Use when an agent must save work state, transfer context, resume another agent's task, or search shared project knowledge.
Why this skill is useful
Provides specific commands and workflows for managing shared context between AI agents that the AI wouldn't reliably generate on its own.
What it needs
Requires ecc-universal installed locally. About 5k tokens when loaded. Last updated 2026-08-06. 238,342 stars on the source repository.
What this skill does
Unified Memory Use the ECC Memory Vault as the common context layer between harnesses. The vault stores portable ecc.memory.v1 Markdown documents rather than harness-specific transcripts or inboxes. Runtime Prerequisite This skill is guidance, not the Memory Vault executable. Skill-only, minimal, manual, and Claude plugin installs do not create the required commands on PATH. Install the ecc-universal npm runtime separately before using the CLI or MCP examples: A repository checkout may instead run the CLI as node scripts/ecc.js memory ..., but MCP configurations that name ecc-memory-mcp still require that binary on PATH. When To Use Save durable context that another agent or later session will need. Hand work from Claude to Codex, Hermes to Claude, or any other harness pair. Resume a task and search for prior decisions, facts, lessons, or handoffs. Diagnose malformed memories, broken links, duplicate IDs, or skipped symbolic links. Do not use the vault as a task tracker, secret store, policy engine, or substitute for governed project documentation. Vault Scopes Scope Location Use --- --- --- project <repo>/.ecc/memory/project/ Repo-local context protected by a fail-closed .gitignore team <repo>/.ecc/memory/team/ Context intended for human review and version-controlled sharing user ~/.ecc/memory/ Operator context that follows the user across repositories All participating harnesses must use the same repository working directory or the same ECCMEMORYPROJECTROOT and ECCMEMORYUSERROOT overrides. Normal search recall covers active project and team memories. A direct ID read may inspect a non-active entry. Request user explicitly with --scope user; it is never included implicitly. Project-scope initialization and writes fail closed if the vault's protective .gitignore exists with unexpected content. Workflow 1. Recall before writing Search for an existing memory before creating another copy: With the opt-in MCP server, use memorysearch and memoryread. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills affaan-m/unified-memory--5020c6