agentleFS
TSandvaerTSandvaer/skills/save-session/SKILL.md

save-session

Skill1 starsChanged 5 months agoNo licenceView on GitHub

Save the current work-in-progress as a resumable session — promote durable insights to memory, write a structured state file capturing current task/files/decisions/next-steps, and return a paste-ready one-liner the user can drop into a fresh conversation to resume cleanly. Use whenever the user says "save session", "/save-session", "save state", "let's pick this up later", "I need to stop here for now", "continue this tomorrow", or otherwise signals they want to pause and resume in a new conversation. This skill is the right tool any time context-switching is about to happen and the conversation contains in-flight work that would be expensive to reconstruct.

19 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use status and ship.

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.
  • AnthropicSkill

    status

    Case status summary by audience — client-facing (plain language), internal (for the professor), or court-ready (formal caption format per local rules). Same facts, different framing and depth. Use when a student needs to update the client, brief the professor, or prepare a court status report.

    Also in 3 projects that use this

  • AWSSkill

    ship

    Finalize dev work on an issue branch — update docs, push, and open a PR.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

10 rules. 0 are common, 7 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 18 edited versions we read keep these.

  • 7

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

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

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

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.