memoryvaultlisted
Install: claude install-skill ayushmall/memoryvault-kit
# memoryvault (Cowork edition)
This is the **zero-install** path to running a personal memory layer. The
[memoryvault-kit](https://github.com/ayushmall/memoryvault-kit) is a CLI tool
for engineers; this skill brings the same idea to Cowork without any local
install. Vault files live in your Google Drive as plain markdown.
If the user is comfortable in a terminal, point them at the kit's CLI for the
full BM25 + graph + reranker pipeline. For everyone else, this skill is the
on-ramp.
---
## How the vault is structured
The skill assumes a folder structure in your Drive. The user is asked to
create or pick one at setup:
```
MyDrive/MemoryVault/
├── memories/2026/ # one .md per memory
├── entities/
│ ├── people/ # one .md per person
│ ├── companies/
│ ├── projects/
│ ├── topics/
│ ├── places/
│ └── roles/
└── INDEX.md # human-readable index, rebuilt periodically
```
Each memory file:
```markdown
---
id: "mem_<source>_<hash>"
title: "Maya escalated dashboard latency Apr 4"
entities: ["[[Maya]]", "[[NorthstarCRM]]"]
tags: ["northstar", "issue", "latency"]
importance: 0.6
source: granola
source_ref: "https://app.granola.so/meeting/abc123"
created: "2026-04-04T10:00:00Z"
updated: "2026-04-04T10:00:00Z"
---
April 4, 2026: Maya escalated that NorthstarCRM users are seeing 6-8
second dashboard latency. Root cause traced to N+1 query in the rendering
path. Raj's team patched within 24h.
```
Each entity file:
```mar