agentleFS
cerebrocybersolutionscerebrocybersolutions/libro/skills/memory-recall/SKILL.md

memory-recall

Skill1 starsChanged 39 days agoApache-2.0View on GitHub

Reads your Libro Brain (session notes, decisions, awareness, dashboard) and tells you what you did or decided over a time window. Read-only and fully local. Use when you ask "what did I work on last week", "what did we decide about X", or "what is still open". Trigger on: "memory recall", "what did I do", "recap my week", "what did we decide", "what's still open".

6 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If you keep notes somewhere else too, name that folder in your ask and recall will read it alongside the Brain.

    line 64
  2. Distinctive:

    Ask it to find gaps: loops opened in one session and never mentioned again.

    line 65

“Common” is measured: kept by at least 6 in 10 of the 5 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

Memory Recall

The skill that proves the memory is real. Your AI reads the Brain that Libro set up on your machine and tells you what you have done, decided, or left open over a window of time. Nothing is uploaded. The Brain sits on your disk.

Where it reads

From your Brain root (the --target you installed into, ~/cerebro-brain by default):

  • master-brain/sessions/ and each department's brain/sessions/: one note per work session, written by sessionend.
  • master-brain/decisions/decisions.md and each department's brain/decisions/: the decisions log.
  • master-brain/awareness.md and master-brain/DASHBOARD.md: the current picture.

On day one these are mostly empty templates, so recall has little to say. It gets sharper every time you close a session with sessionend.

What it does

  1. Lists the session notes and decision entries in the window you ask for (file dates and the dates inside the notes).
  2. Reads them, plus awareness and the dashboard for the current state.
  3. Returns a short recap: what you worked on, what you decided, what is still open.
  4. Quotes the file it got each point from, so you can open it and check.

Scope

  • Reads: your Brain folder only. Nothing leaves your machine.
  • Writes: nothing. This skill is read-only by design.
  • Reaches: nothing. Fully local.

How to use it

Tell your AI:

Use memory recall. What did I work on last week? Give me a short recap and anything still open.

Other ways to ask:

What did we decide about pricing? Read the Brain and quote the decision with its file.

Summarize everything in the Brain from this month, grouped by department.

What did I say I would do but have not closed?

Make it yours

  • The more you write to the Brain, the sharper recall gets. Close each work session with sessionend, or add one line to the day's session note yourself.
  • If you keep notes somewhere else too, name that folder in your ask and recall will read it alongside the Brain.
  • Ask it to find gaps: loops opened in one session and never mentioned again.

Ships with the Libro libro-starter profile. Your AI. Your machine. Your rules.

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.