agentleFS
Sign inStart free
arnaugonzalezarnaugonzalez/memory-boost/skills/restore-session/SKILL.md

restore-session

Skill0 starsChanged 47 days agoMITView on GitHub

Load context from the shared agent memory before continuing work on a project - latest sessions, pending items, open checkpoints. Use when the user says "restore session", "where were we", "catch me up" or starts work on a project without a SessionStart hook.

4 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions4 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 4

    1. shkodnik1917/claude-brainlab★ 35same name
    2. Vepricov/claude-brainlab★ 35same name
    3. ZENG3LD/claude-session-restore★ 35same name
    4. ZENG3LD/session-restore★ 35same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository5 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 0

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

    If a previous session of yours may be unfinished, call memory_resume(project, session_id).

    line 9

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

restore-session

  1. Call memory_brief(project=<cwd or project name>).
  2. If a previous session of yours may be unfinished, call memory_resume(project, session_id).
  3. For anything the brief only hints at, use memory_recall(query, project) and then memory_page(name, section) for the relevant section. Do not read whole pages by default.
  4. Reply with a short "where we left off": last actions, pending items, active parallel sessions (so you don't step on their files), and the next concrete step you propose.

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