agentleFS
Sign inStart free
apappascsapappascs/claude-code-sessions/skills/session-memory-search/SKILL.md

session-memory-search

Skill2 starsChanged 26 days agoMITView on GitHub

Searches across all Claude Code memory file contents by keyword. Use when the user asks to find something in their memories, search stored knowledge, or locate a specific memory by content rather than name. Also triggered by: "search memories for", "find in memories", "which memory mentions".

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read the full file — use the Read tool on the path field

    line 41
  2. Very specific:

    Check health — suggest /session-memory-audit

    line 43

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Step 1: Run the search

bun run ${CLAUDE_PLUGIN_ROOT}/lib/memory-scanner.ts search "<query>" --limit 20 --context 1

Replace <query> with the user's search term. Add filters based on request:

  • --type user|feedback|project|reference — filter by memory type
  • --project FILTER — filter by project name
  • --context N — lines of context around each match (default 1)
  • --limit N — max results (default 20)

Step 2: Present the results

Output is NDJSON (one JSON object per line). Parse each line and group results by project.

For each project with matches:

Project: project-name

FileTypeLineMatch
filename.mdtypeNmatched text (trimmed)

Show context lines (if available) indented below each match.

If no results: Suggest broadening the search or trying alternative keywords.

Step 3: Offer actions

For each matched memory file, the user might want to:

  • Read the full file — use the Read tool on the path field
  • Edit the memory — use the Edit tool on the path field
  • Check health — suggest /session-memory-audit

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free