agentleFS
manastalukdarmanastalukdar/ai-devstudio/skills/session-resume/SKILL.md

session-resume

Skill1 starsChanged 7 months agoMITView on GitHub

Resume previous work from archived session with full context restoration

10 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use eval-harness.

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.

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

    Check for an active session by reading the .claude/sessions/.current-session file.

    line 9
  2. Distinctive:

    If the file is empty or doesn't exist, inform the user that there is no active session to resume and stop the process.

    line 10
  3. Distinctive:

    If the file exists, read contents and provide summary to user.

    line 11
  4. Distinctive:

    Caching: No persistent caching beyond the session file itself.

    line 17

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

Claude Session Resume

  1. Check for an active session by reading the .claude/sessions/.current-session file.
  2. If the file is empty or doesn't exist, inform the user that there is no active session to resume and stop the process.
  3. If the file exists, read contents and provide summary to user. Also provide points on possible next steps to potentially resume that session.

Token Optimization

Expected range: 200–600 tokens (initial), 100 tokens (cache hit)

Caching: No persistent caching beyond the session file itself.

Early exit: Returns immediately if the named session does not exist.

Patterns used: Early exit, caching (session files)

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.