agentleFS
YehudaFrankelYehudaFrankel/clankbrain/.claude/skills/recall/SKILL.md

recall

Skill16 starsChanged 7 months agoMITView on GitHub

Natural language memory search. Use when the user asks "what did we decide about X", "do we know anything about X", "have we dealt with X before", or "/recall X". Faster than search-memory — single grep pass, no parallel agents.

142 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use addskill, apply-firmware and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • ryanportfolioSkill

    addskill

    Create, import, update, or install repo or personal skills: runtime ownership, resources, discovery checks.

    Also in 6 projects that use this

  • ryanportfolioSkill

    apply-firmware

    Bring current folder (plain folder, existing repo, old or partial firmware copy) up to full Harness Firmware in place. Mirror external repo → adopt-repo.

    Also in 6 projects that use this

  • +10 more from ryanportfolio

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 129 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run this via Bash. If semantic search returns no matches, also run keyword search:

    line 34
  2. Distinctive:

    If a result looks relevant but partial:

    line 63
  3. Distinctive:

    Never write or modify memory files in this skill — read only

    line 69
  4. Very specific:

    If memory.py is not found, fall back to: Grep(pattern="[query]", path="[MEM]") recursively

    line 70

“Common” is measured: kept by at least 6 in 10 of the 129 edited versions of this file we could read. “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

Skill: recall

Trigger phrases:

  • /recall [question or topic]
  • "what did we decide about X"
  • "do we know anything about X"
  • "have we seen X before"
  • "what's in memory about X"
  • Any quick single-topic lookup

Use search-memory instead when: the question could span 3+ memory categories and you want parallel agents with a synthesized answer.


Steps

Step 1 — Extract the query

Pull the search term(s) from the user's message. If it's a full question ("why did we move files to mobile/?"), extract the key nouns: "mobile files location".

Step 2 — Run the search

Try semantic search first (finds related memories even with different wording). Falls back to keyword search automatically if the index doesn't exist or sentence-transformers isn't installed.

python tools/memory.py --search-semantic "[query]" --top 8

Run this via Bash. If semantic search returns no matches, also run keyword search:

python tools/memory.py --search "[query]" --top 8

Step 3 — Present results

If results found:

## Recall: "[query]"

**[file name]** (score N)
> [matching lines]

**[file name]** (score N)
> [matching lines]

---
Bottom line: [1 sentence summary of what memory says]

If nothing found:

No memory found for "[query]".

This topic hasn't been captured yet. If it comes up this session, run /learn at the end to save it.

Step 4 — Offer to dive deeper

If a result looks relevant but partial:

"Found in lessons.md — want me to read the full entry?"


Notes

  • Never write or modify memory files in this skill — read only
  • If memory.py is not found, fall back to: Grep(pattern="[query]", path="[MEM]") recursively
  • This skill is intentionally fast — no agents, no synthesis overhead
  • For broader research across multiple categories, use search-memory

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.