agentleFS
freskhufreskhu/genesis/.claude/skills/session-end/SKILL.md

session-end

Skill5 starsChanged 6 months agoApache-2.0View on GitHub

Run the mandatory Session End Protocol (palace and twin updates, diary, activity log, kaizen backlog, lessons learned, procedural audit, memory-hot regen)

30 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use 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.
  • 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

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 23 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read that file and execute the steps in order:

    line 14
  2. Distinctive:

    Do NOT duplicate or fork the step logic here — edit the protocol file instead.

    line 28

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

Session End Protocol — wrapper

This skill is a thin wrapper. The canonical, single source of truth is:

.claude/protocols/session-end.md

Read that file and execute the steps in order:

  1. Palace and twin updates (palace.py add / kg-add / kg-invalidate, plus /twin-update)
  2. Diary entry (AAAK format, palace.py diary-write)
  3. Activity log (session_end)
  4. Kaizen backlog surface (only when 3+ [Kaizen] proposals have been pending >48h)
  5. Lessons learned and system improvement (feedback memory / procedural memory / palace)
  6. Procedural memory audit (BLOCKING — enumerate delegations, capture non-obvious patterns)
  7. Regenerate memory hot (python3 scripts/generate_memory_hot.py)

The protocol is enforced by the force-session-end.sh (Stop) hook, which blocks the close until lessons, procedural audit and memory-hot regeneration are evidenced.

Do NOT duplicate or fork the step logic here — edit the protocol file instead. Two copies of a protocol drift, and the copy the agent happens to read wins.

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.