MemFS Search

Semantic search over agent memory files — find conceptually related memory blocks, discover forgotten reference files, and check what you…

You say
Buy it · $24 Read it before you buy $24 Written by letta-ai · unverified publisher
Context cost
2.9k tokensestimated from the bundle, loaded when it triggers
Bundle
3 files · 11.6 kB1 script among them — read before you run
Licence
MITpaid listing
Last change
no release on file
Servers it uses
Noneruns standalone

What it does

Semantic search over agent memory files. Use when you need to find conceptually related memory blocks, discover forgotten reference files, check what you already know before creating new memory, or search beyond exact keyword matching. Currently supports QMD (local, no API keys).

Installed, it changes the agent in these ways.

What this skill changes about the agent is not written down here yet. The listing was collected from its source, and the description is in its own SKILL.md.

Workflow

Runs a procedure end to end.

memorysemantic-searchlettamemfs

The skill itself

This is the whole product. A skill is instructions the model reads, so there is nothing behind the listing you cannot see first — the front matter loads with every session, and the body below it loads when the skill triggers.

SKILL.md3.6 kB · 102 lines
--- name: memfs-search description: Semantic search over agent memory files. Use when you need to find conceptually related memory blocks, discover forgotten reference files, check what you already know before creating new memory, or search beyond exact keyword matching. Currently supports QMD (local, no API keys). ---
6# MemFS Search
7
8Semantic search over your memory filesystem. Useful when Grep isn't enough — finding conceptually related blocks, discovering forgotten reference files, or answering "what do I know about X" across all memory.
9
10## Setup
11
12First time only. Run the setup script to create the index and generate embeddings:
13
14```bash
15bash <SKILL_DIR>/scripts/memfs-search.sh setup
16```
17
18This creates a QMD collection over $MEMORY_DIR, adds context annotations, and embeds all .md files. First run downloads ~2GB of local GGUF models to ~/.cache/qmd/models/.
19
20For installation, embedding model options, and troubleshooting: [references/qmd-setup.md](references/qmd-setup.md).
21
22## Searching
23
24Three tiers. Pick based on what you know about your query:
25
26| You have... | Use | Command | Speed |
27|-------------|-----|---------|-------|
28| An exact term or phrase | **keyword** | search | ~0.3s |
29| A vague concept ("what do I know about X") | **semantic** | vsearch | ~2s cold, <1s warm |
30| No idea, need the best results | **hybrid** | query | ~3s cold, <1s warm |
31
32```bash
33S="bash <SKILL_DIR>/scripts/memfs-search.sh"
34
35# Keyword — fast, use first
36$S search "lettabot architecture"
37
38# Semantic — conceptual, use when keyword misses
39$S vsearch "how does the user feel about code reviews"
40
41# Hybrid — best quality, uses keyword + vectors + reranking
42$S query "projects cameron is working on"
43```
44
45**Always start with keyword search.** Only escalate when it misses. Hybrid is 10x slower than keyword.
46
47### Output Formats
48
49All commands accept output flags forwarded to QMD:
50
51```bash
52$S search "topic" --json # structured (for processing)
53$S search "topic" --files # file paths only (pipe into Read)
54$S search "topic" --full # full document, not snippet
55$S search "topic" -n 15 # more results (default: 5)
56```
57
58--json returns an array of objects with file, score, snippet, and context fields.
59
60### Retrieval
61
62Fetch a specific file or batch of files without searching:
63
64```bash
65# Single file
66qmd get "system/human/identity.md" -c memory --full
67
68# Batch by glob
69qmd multi-get "reference/projects/*" -c memory
70```
71
72## When to Search Proactively
73
74Don't wait to be asked. Search memory when:
75
761. **Before creating a new memory file** — check if the topic already exists. $S search "topic" --files tells you instantly.
772. **User asks "do you know about X"** — search before saying no. Reference files you haven't loaded recently might have it.
783. **During /init or memory reorg** — verify coverage. Search for key concepts and confirm they're stored somewhere.
794. **Debugging "I told you about this"** — the user thinks you should know something. Search memory before falling back to message history.
80
81## Maintenance
82
83After bulk memory changes (e.g. after /init, reorganization, creating many files):
84
85```bash
86bash <SKILL_DIR>/scripts/memfs-search.sh reindex
87```
88
89Check index health:
90
91```bash
92bash <SKILL_DIR>/scripts/memfs-search.sh status
93```
94
95## When NOT to Use
96
97- Exact string matching — use Grep.
98- Finding files by name/pattern — use Glob.
99- Reading a file you already know the path to — use Read.
100- Searching message history — use the searching-messages skill.
101- The query is a single word that would match literally — keyword Grep is faster.
102
In the file
SKILL.md552 words
Files3
LicenceMIT
Why you can read it

Nothing in a skill executes. The client loads the text and the model follows it, so a skill can be audited the way a runbook is — by reading it.

What it costs in context

Skills are not billed by the call. They are paid for in context: every token the instructions occupy is a token your code, your diff and your conversation cannot use. Here is what this one takes and when it takes it.

≈80
always loaded
The name and description, so the model knows the skill exists and when to reach for it.
2,820
on trigger
The instruction body and 2 supporting files, read only when the skill fires.
1.5%
of a 200k window
Ten skills this size would take about 15% of the window before you open a file.
050k100k150k200k context window

2.9k tokens, estimated from the bundle at four bytes to the token, held for the rest of the session once it triggers. Middling. Fine to keep on in a project where you use it weekly, worth unloading in one where you never do.

Servers bill, skills cost

A server charges by the month. A skill charges once per session, in context, and then keeps charging it for as long as the session lives.

Before and after

The same question, put to the same model twice: once as it comes, and once with these instructions loaded.

No worked example has been published for this skill yet.

Adoption
Installsnone yet
Ratingno reviews yet

The procedure it runs

The procedure has not been published here. It is in the skill’s own SKILL.md, which its author has not sent to the marketplace yet.

Prose, not code

These steps are written for a model to follow, not executed by a runtime. It can still be told to skip one, and it will say so when it does.

Servers it uses

None. This skill calls no MCP servers at all.

Everything it needs is in the instructions, so it works in a project with nothing connected — the model reads the file and changes how it works with what it can already reach.

It writes no files and reaches no network. All it changes is how the model reasons and writes.

What it asks for
Writes filesno
Network accessno

Read from the allowed-tools line of this skill’s own SKILL.md. A skill grants no permissions of its own — it can only ask for tools your client already has.

What it will not do

Every skill is narrow, and the useful ones say where they stop. These are the jobs this one is the wrong tool for.

What this skill is not for has not been published here. Nothing is implied by that: it is a section the author has not filled in.

What is in the bundle

3 files, 11.6 kB on disk. Mostly text — the instructions the model reads — with 1 script in it that your client would run only if the instructions tell it to.

  • SKILL.md3.6 kB
  • references/qmd-setup.md2.5 kB
  • scripts/memfs-search.sh5.5 kB
What is not in it

A skill installs nothing and depends on nothing: it is a folder your client reads. This one carries 1 script beside the text, so the bundle is 3 files you can review in full before installing. The MIT licence covers the templates and examples as well as the instructions.

Install

Installing copies the bundle into your project. Nothing runs at install time — the files sit on disk until the model reads them.

$24 once
MemFS Search · MIT · letta-ai
one-time
Price$24 once
LicenceMIT — the author’s, unchanged by this purchase
Paid throughStripe, once, on the card you add at the checkout
Keeps workingfor good — the files are yours once they are on disk
Updatesevery update its author ships, delivered through this account

You can read the whole bundle before paying — the SKILL.md above is the product, not a preview of it. What the money buys is the delivery: the folder packaged and handed to your machine by key, every update its author ships, and our support if it does not do what this listing says. The terms of use are MIT, set by the author and unchanged by buying it here.

Payment runs through Stripe, on a page like this one rather than a redirect. Once there is an account it joins the same mcprush invoice as everything else you run, so there is never a second card to enter.

Which clients pick it up on their own

A skill is a folder of text. A client with a skills folder reads it without being told; everywhere else the same text works, it is just handed to the model rather than found.

Claude Code.claude/skills/
Claude Desktop
ChatGPT
Cursor.cursor/skills/
VS Code.github/skills/
Codex CLI.agents/skills/
Gemini CLI.gemini/skills/
Grok.grok/skills/
Zed.agents/skills/
Windsurf.windsurf/skills/
Agent SDK.claude/skills/
HTTP / API
This release
Versionnot versioned
Publishedno release date on file
Price$24
Referenceletta-ai/memfs-search

Versions

Its author publishes no version number, so there is nothing here to pin to: what you install is the folder as it stands today. Instructions change more often than APIs do — a skill can be rewritten entirely without anything it depends on moving.

v
  • No earlier releases have been published to the marketplace.
Pinning

Nothing to pin to: this skill carries no version number of its own. What you install is what the folder holds on the day you install it.

Reviews

no reviews yet · no installs yet

Nobody has reviewed this skill yet. The rating is the mean of the reviews written here, so there is none until somebody writes the first.

Who can post

Only accounts that have had the skill installed for fourteen days, so a review is written after living with it rather than after reading it. Publishers may reply once.

Who wrote it

LE
letta-ai

Publishes on mcprush.

0 servers listed2 skills listednot claimed
Profile
Publisher
Servers0