session-end

To persist a structured session summary at the work session end, provide the required closure fields such as intent, state delta, and next actions. The skill validates these inputs, performs PII scrubbing, and stores the session state for continuity.

A structured session closure note includes a final summary, working set, state delta, open loops, next actions, and closure status. Capturing these elements ensures seamless resumption by documenting decisions and outcomes for the next session.

Yes, you can sync session state updates to Notion when wrapping up a work session. The skill optionally updates connected knowledge stores like Notion while persisting the structured summary and scrubbing sensitive information.

PII scrubbing during session state delta storage removes sensitive personal information while preserving non-sensitive structured fields. This ensures the persisted summary and working set remain safe for knowledge store updates without losing critical technical context.

Mandatory fields required to generate a valid session closure summary include the summary, intent, working set, state delta, open loops, next actions, and closure status. Providing all required fields ensures the structured note is successfully drafted and persisted.

Yes, session closure works without external dependencies for local knowledge persistence. The skill drafts and stores the structured session summary independently, while Notion integration remains an optional configuration for remote knowledge store updates.