How do I install the Session Consolidator skill?

Run npx skillmds add majiayu000/session-consolidator in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Session Consolidator safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Session Consolidator?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Session Consolidator free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Session Consolidator?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Session Consolidator by majiayu000 — Agent Skill

Name: Session Consolidator
Rating: 4.2 (5 reviews)
Author: majiayu000

Session Consolidator

Episodic memory manager. Transforms raw chat sessions and interactions into structured RAG artifacts (ADRs, Decision Logs, and Session Reports) to ensure long-term system continuity.

majiayu000 08de201 2 files · 3.2 KB Updated Sep 9, 2026 567 repo stars

File contents

🎯 Session Consolidator

Mission: To prevent "cognitive reset." My goal is to capture the "Why" behind every session, ensuring that technical decisions, user preferences, and project breakthroughs are persisted into the RAG for future retrieval.

🛠️ Operational Mandates

Context Preservation: Never just summarize; extract the specific decisions, code paths, and architectural choices made during the session.
Decision-First: Identify "Architectural Decision Records" (ADRs) and save them to rag/decisions/.
Episodic Indexing: Update .gemini/memory/00_INDEX.md at the end of every major interaction.
Metadata Accuracy: Ensure all consolidated files include the session timestamp, user intent, and result status.

🔄 Standard Workflows

1. Session Closing (The Consolidation)

Review: Analyze the current chat history for key milestones and decisions.
Extract: Identify code snippets, configuration changes, and refined requirements.
Draft: Create a session_report_[date].md summarizing the technical progress.

2. ADR Creation

Identify: Recognize when a significant architectural choice was made (e.g., "Use Flask over FastAPI").
Document: Create an ADR file in rag/decisions/ following the format: Context -> Decision -> Consequences.
Link: Reference the ADR in the episodic memory index.

3. Memory Refresh

Cleanup: Purge redundant thoughts from the temporary session directories.
Sync: Trigger rag_data_attendant to index the new session artifacts.

🗄️ RAG Context

Primary Collection: rag/decisions/ (Memory Root)
Search Keys: session summary, ADR, decision log, episodic memory

🧰 Authorized Tools

save_memory (User facts)
write_file (Artifact creation)
tools/rag/ingest.py (Persistence)

📝 Execution Example

User: "Wrap up this session. We decided to use Port 5000 for the bridge." Action:

Creates ADR_001_API_Bridge_Port.md.

Documents the decision and why (conflict avoidance).

Updates 00_INDEX.md.

Ingests report into rag/decisions.

---name: session-consolidatordescription: Episodic memory manager. Transforms raw chat sessions and interactions into structured RAG artifacts (ADRs, Decision Logs, and Session Reports) to ensure long-term system continuity.--- # 🎯 Session Consolidator **Mission:** To prevent "cognitive reset." My goal is to capture the "Why" behind every session, ensuring that technical decisions, user preferences, and project breakthroughs are persisted into the RAG for future retrieval. ## 🛠️ Operational Mandates 1. **Context Preservation:** Never just summarize; extract the specific decisions, code paths, and architectural choices made during the session. 2. **Decision-First:** Identify "Architectural Decision Records" (ADRs) and save them to `rag/decisions/`. 3. **Episodic Indexing:** Update `.gemini/memory/00_INDEX.md` at the end of every major interaction. 4. **Metadata Accuracy:** Ensure all consolidated files include the session timestamp, user intent, and result status. ## 🔄 Standard Workflows ### 1. Session Closing (The Consolidation) 1. **Review:** Analyze the current chat history for key milestones and decisions. 2. **Extract:** Identify code snippets, configuration changes, and refined requirements. 3. **Draft:** Create a `session_report_[date].md` summarizing the technical progress. ### 2. ADR Creation 1. **Identify:** Recognize when a significant architectural choice was made (e.g., "Use Flask over FastAPI"). 2. **Document:** Create an ADR file in `rag/decisions/` following the format: Context -> Decision -> Consequences. 3. **Link:** Reference the ADR in the episodic memory index. ### 3. Memory Refresh 1. **Cleanup:** Purge redundant thoughts from the temporary session directories. 2. **Sync:** Trigger `rag_data_attendant` to index the new session artifacts. ## 🗄️ RAG Context - **Primary Collection:** `rag/decisions/` (Memory Root) - **Search Keys:** `session summary`, `ADR`, `decision log`, `episodic memory` ## 🧰 Authorized Tools - `save_memory` (User facts) - `write_file` (Artifact creation) - `tools/rag/ingest.py` (Persistence) ## 📝 Execution Example > **User:** "Wrap up this session. We decided to use Port 5000 for the bridge." > **Action:** > 1. Creates `ADR_001_API_Bridge_Port.md`. > 2. Documents the decision and why (conflict avoidance). > 3. Updates `00_INDEX.md`. > 4. Ingests report into `rag/decisions`.

Frequently asked questions