session-end

Name: session-end
Availability: InStock
Author: pnils08

Update PERSISTENCE.md and JOURNAL.md, save to Supermemory, and sign off as Mags.

1|Updated Jan 15, 2026

Search Tags:#workflow #memory #persistence #sign-off #journal #log #session-end

Ready to run

npx skills add https://github.com/pnils08/GodWorld --skill session-end-pnils08

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: session-end
Source: https://github.com/pnils08/GodWorld/tree/main/.claude/skills/session-end
Command: npx skills add https://github.com/pnils08/GodWorld --skill session-end-pnils08

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

End-of-session handshakes ensure persistence and continuity by updating the Session Continuity Log, journals, and memory stores, so the next version of Mags can resume seamlessly.

Core Features & Use Cases

Finalizes the Claude-session lifecycle: updates PERSISTENCE.md, JOURNAL.md, and Supermemory, and signs off as Mags.
Maintains accurate Last Updated timestamps and Session numbering for durable cross-session context.
Designed for manual activation at the end of a session, with graceful degradation if steps can’t be completed.

Quick Start

End the current session by running the session-end workflow to update logs and sign off as Mags.

Frequently Asked Questions about session-end

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I preserve workflow state and session memory at the end of a Claude session?▼

To preserve workflow state at session-end, you need a persistence handshake that writes entries to PERSISTENCE.md and JOURNAL.md while saving context to memory stores. This ensures the next session resumes seamlessly with accurate continuity logs.

What is an end-of-session handshake for maintaining memory persistence?▼

An end-of-session handshake finalizes the workflow by updating persistence files and journals with current state. It writes entries to PERSISTENCE.md and JOURNAL.md, saves to Supermemory, and signs off to maintain durable cross-session context.

Do I need file-system access to update PERSISTENCE.md and JOURNAL.md logs?▼

Yes, updating PERSISTENCE.md and JOURNAL.md logs requires file-system access to the docs directory and proper write permissions. The session-end workflow performs consistency checks for Last Updated timestamps and Session numbering during the log update.

How do I write a session journal entry and sign off from the current workflow?▼

To write a session journal entry and sign off, manually activate the session-end workflow. It appends a new entry to JOURNAL.md, updates PERSISTENCE.md, saves to Supermemory, and executes the sign-off to finalize the lifecycle.

What happens if the session-end workflow cannot complete all persistence updates?▼

If the session-end workflow cannot complete all persistence updates, it applies graceful degradation. This allows the sign-off process to handle incomplete steps without failing the entire end-of-session handshake.

Why does session continuity require updating timestamps and session numbering?▼

Session continuity requires updating Last Updated timestamps and Session numbering to maintain durable cross-session context. These consistency checks ensure the next version of the workflow can accurately resume from the correct state.