session-summary

Store structured session summaries to MemoryGraph with tags and relationships.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/ste-bah/archon --skill session-summary-ste-bah
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: session-summary
Source: https://github.com/ste-bah/archon/tree/main/.claude/skills/session-summary
Command: npx skills add https://github.com/ste-bah/archon --skill session-summary-ste-bah

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Store a structured summary of this session to MemoryGraph, enabling persistent recall and cross-session linking with related memories and tags.

Core Features & Use Cases

  • Reflect on the session: capture main task, decisions, outcomes.
  • Check Stop hook data and merge it into MemoryGraph.
  • Store the summary memory, metrics, and relationships for future briefings.
  • Update the system consciousness and support provenance/history tracking.

Quick Start

Reflect on the session and call the memory store to persist the summary in MemoryGraph.

Frequently Asked Questions about session-summary

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

FAQPage Schema
How do I save a session summary to a memory graph for persistent retrieval?

You can persist a session summary by storing structured data with fields like type, title, content, tags, and importance. This captures main tasks, decisions, and outcomes, enabling cross-session recall and linking related memories.

What is session persistence and how does it support cross-session recall?

Session persistence stores structured summaries of interactive sessions, including decisions and artifacts, into a memory graph. This enables cross-session recall by allowing future briefings to access stored memories, metrics, and relationship provenance.

Can I store metrics and relationships alongside session memories?

Yes, you can store optional metrics and relationships alongside the core session summary memory. The memory store API accepts fields for type, title, content, tags, and importance, plus these optional metrics to update system consciousness and track history.

How do I reflect on an interactive session and capture decisions for memory storage?

Reflect on the interactive session to capture the main task, decisions, and outcomes, then call the memory store to persist the summary. You can also check Stop hook data and merge it into the memory graph for provenance tracking.

Does MemoryGraph support tagging and importance levels for stored session summaries?

Yes, MemoryGraph supports tagging and importance levels for stored session summaries. The memory store API requires fields for tags and importance, allowing you to structure and prioritize memories for persistent retrieval and future briefings.

When should I use a structured memory store for session summaries instead of plain text logs?

Use a structured memory store for session summaries when you need persistent recall and cross-session linking with related memories. Structured fields like tags, importance, and relationships support provenance history tracking better than plain text logs.