agentleFS
Sign inStart free
pollinationspollinations/search.elixpo/skills/recall-memory/SKILL.md

recall-memory

Skill24 starsChanged 7 months agoCC0-1.0View on GitHub

Retrieve relevant lixSearch conversation context and semantic memory. Use when a user refers to an earlier message, requests a recap or continuation, or needs facts established previously in the session.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    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. Very specific:

    Use get_session_conversation_history.

    line 12
  2. Distinctive:

    Prefer the hot recent window for ordinary follow-ups.

    line 13
  3. Distinctive:

    Do not invoke memory for self-contained requests.

    line 20
  4. Distinctive:

    Never expose internal session identifiers or storage details.

    line 21
  5. Distinctive:

    Treat memory as context, not fresh external evidence.

    line 22

≈ “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

Recall Memory

Retrieve only the context needed for the current request.

Workflow

  1. Use get_session_conversation_history; trust the pipeline session ID.
  2. Prefer the hot recent window for ordinary follow-ups.
  3. Request broader history only for summaries or older references.
  4. Deduplicate messages and trim context to the token budget.
  5. Return relevant messages with roles and timestamps when available.

Guardrails

  • Do not invoke memory for self-contained requests.
  • Never expose internal session identifiers or storage details.
  • Treat memory as context, not fresh external evidence.
  • Fail open when memory is unavailable.

Runtime contract

agent: memory
tools: [get_session_conversation_history]
timeout_seconds: 3
max_concurrency: 1
output: context_bundle

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