session-reflection

Extract agreements, open items, and crystallization opportunities into a three-section session reflection.

3|1|Updated Nov 10, 2025
One-click install
npx skills add https://github.com/metraton/gaia --skill session-reflection-metraton
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: session-reflection
Source: https://github.com/metraton/gaia/tree/main/skills/session-reflection
Command: npx skills add https://github.com/metraton/gaia --skill session-reflection-metraton

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

End of a conversational session, it provides a concise, structured reflection focused on agreements and decisions rather than actions, helping close the loop with the user.

Core Features & Use Cases

  • Three-section output: "What we agreed", "What remained open", "What deserves crystallization" presented in user language.
  • Non-persistence by default: Keeps memory untouched unless user opts in.
  • Guided closure: Supports orchestration flows by surfacing key outcomes at session end.

Quick Start

Provide a short, structured reflection at the end of a session, citing 2-4 agreements, any open items, and recommended crystallization ideas.

Frequently Asked Questions about session-reflection

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

FAQPage Schema
How do I generate a session reflection that captures agreements and open items?

To generate a session reflection, the skill extracts agreements, open items, and crystallization opportunities from your conversation. It delivers a three-section summary covering what was agreed, what remained open, and what deserves crystallization.

What is session closure in conversational orchestration and when do I need it?

Session closure in conversational orchestration is the process of summarizing meaningful conversational weight at the end of a session. You need it to close the loop with users by surfacing key outcomes and crystallizing decisions rather than just listing actions.

Does the session reflection output persist agreements to memory automatically?

No, the session reflection output does not persist agreements to memory automatically. It keeps memory untouched by default and adheres to user privacy controls unless you explicitly opt in to save the summarized outcomes.

Can I use session reflection for lightweight chats or does it require meaningful conversational weight?

Session reflection is applicable to sessions with meaningful conversational weight. It is designed to capture the conversational arc from agreements to future follow-ups, making it less suitable for lightweight or trivial interactions.

What's the best way to structure end-of-session summaries for orchestrator flows?

The best way to structure end-of-session summaries for orchestrator flows is using a three-section format: What we agreed, What remained open, and What deserves crystallization. This guided closure surfaces 2-4 key agreements and recommended crystallization ideas.

Are there limitations to using session reflection for capturing open items?

A limitation of using session reflection is that it focuses strictly on agreements and decisions rather than tracking granular action items. It surfaces open items for future follow-ups but does not function as a persistent task management system.