agentleFS
Sign inStart free
faizkhairifaizkhairi/claude-code-blueprint/skills/load-session/SKILL.md

load-session

Skill73 starsChanged 4 months agoMITView on GitHub

Restore session context at the start of every new conversation. Auto-triggers on session start, or when user says 'continue', 'what were we doing', 'where did we leave off'.

The file

We split this skill into the rules it gives an agent

11 rules. About 0 are common, 3 are distinctive, and 8 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 8

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Prerequisite check (run first): if ./memory/ does not exist OR ~/.claude/.memory-disabled marker file is present, this skill is a no-op.

    line 7
  2. Very specific:

    Read ./memory/core/session.md for where we left off

    line 11
  3. Very specific:

    Read ./memory/core/preferences.md for user preferences

    line 12
  4. Very specific:

    Read {MEMORY_MD_PATH} for technical context and project conventions

    line 13
  5. Very specific:

    Read ./memory/core/reminders.md for active reminders

    line 14
  6. Very specific:

    Read ./memory/core/decisions.md for architectural decision context

    line 15
  7. Very specific:

    Check ./memory/diary/current/ for the most recent diary entry (if any)

    line 16
  8. Very specific:

    Check ./memory/projects/active/ for active project files (scan directory)

    line 17
  9. Distinctive:

    Check CLAUDE.md for topic file references relevant to the current project

    line 19
  10. Distinctive:

    Only load topic files related to the current working directory

    line 20
  11. Distinctive:

    Keep the summary brief and actionable, focusing on what's needed to continue working effectively.

    line 31

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

Prerequisite check (run first): if ./memory/ does not exist OR ~/.claude/.memory-disabled marker file is present, this skill is a no-op. Output: "Memory persistence is disabled. Run ./setup.sh and choose to enable memory if you want this skill to work."

Restore context from the memory system:

  1. Read ./memory/core/session.md for where we left off
  2. Read ./memory/core/preferences.md for user preferences
  3. Read {MEMORY_MD_PATH} for technical context and project conventions
  4. Read ./memory/core/reminders.md for active reminders
  5. Read ./memory/core/decisions.md for architectural decision context
  6. Check ./memory/diary/current/ for the most recent diary entry (if any)
  7. Check ./memory/projects/active/ for active project files (scan directory)
  8. Read relevant topic files based on project context:
    • Check CLAUDE.md for topic file references relevant to the current project
    • Only load topic files related to the current working directory
  9. Summarize in a concise format:
    • Reminders: Display open reminders prominently at the top with any deadlines highlighted
    • Last session: What we were working on and where we left off
    • Pending: What's still in progress or needs attention
    • Active projects: Current project(s) and their session context
    • Priorities: Current goals and focus areas
    • Blockers: Any open questions or issues from last session
    • Preferences: Key communication and work style preferences

Keep the summary brief and actionable, focusing on what's needed to continue working effectively.

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