memory

Name: memory
Availability: InStock
Author: cgm-free

Persist cross-session notes, decisions, and session data in a local .memory structure.

Updated Mar 16, 2026

Search Tags:#decisions #context #adr #memory #notes #sessions #cross-session

Ready to run

npx skills add https://github.com/cgm-free/ai-education-platform --skill memory-cgm-free

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: memory
Source: https://github.com/cgm-free/ai-education-platform/tree/main/.agents/skills/memory
Command: npx skills add https://github.com/cgm-free/ai-education-platform --skill memory-cgm-free

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, glab, jq, and includes scripts (resource) components.

What problem does it solve?

Persist cross-session knowledge to inform future interactions.

Core Features & Use Cases

Cross-session memory for decisions, notes, todos, and session history.
ADRs and context carryover to new sessions and handoffs.
Seamless integration with local and remote storage to enable long-running projects.

Quick Start

Create a new memory context and start recording notes, decisions, and context to enable cross-session continuity.

Frequently Asked Questions about memory

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

FAQPage Schema

How do I persist context and decisions across multiple coding sessions?▼

Cross-session memory is maintained by capturing notes, decisions, and session data into a local .memory structure, enabling context and ADR carryover for future interactions and project handoffs.

What is the best way to keep ADRs and notes alive during long-running project handoffs?▼

Using cross-session memory preserves ADRs and notes by storing them locally with optional remote sync, ensuring continuity and context retrieval during long-running project handoffs.

Do I need specific CLI tools to set up cross-session memory and notes?▼

Yes, setting up cross-session memory requires dependencies including gh, glab, and jq, alongside supporting scripts to capture and manage the local .memory structure effectively.

How does remote sync work for preserving session history and context?▼

Remote sync for session history integrates with local storage to enable long-running projects, allowing captured notes and decisions to be synchronized across environments and team members.

Can I use this memory approach for multi-session explorations and todos?▼

Yes, cross-session memory is applicable to multi-session explorations, persisting todos, context, and session history to maintain continuity throughout extended research and development tasks.

Why does cross-session context break without a local .memory structure?▼

Without a local .memory structure and supporting scripts, there is no persistent repository to capture notes and decisions, causing context and ADRs to be lost between separate sessions.