session-memory

Write and read structured notes across project and cross-project sessions.

1|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/kiryteo/opencode-setup --skill session-memory-kiryteo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: session-memory
Source: https://github.com/kiryteo/opencode-setup/tree/main/skills/session-memory
Command: npx skills add https://github.com/kiryteo/opencode-setup --skill session-memory-kiryteo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Continual note-taking system that makes agents progressively better at recurring tasks. Write structured learnings after working in unfamiliar areas. Read them before starting work. Notes are for agent consumption, not human documentation.

Core Features & Use Cases

  • Two Storage Locations: Project-Level Notes (.opencode/notes/) and Cross-Project Notes (~/.config/opencode/notes/), enabling both context-specific and universal patterns.
  • Note Format & Lifecycle: Structured templates with Last updated, Key Facts, Gotchas, Patterns, and Related Files, guiding consistent knowledge capture and reuse.
  • When to Write & Read: Write notes after exploring unfamiliar code, and read relevant notes before new tasks to inform decisions.
  • Interaction Log: Automatically log substantive sessions to a dedicated memory file for traceability.
  • Cross-Session Tracking: Plan and checkpoint memory to persist knowledge across sessions.

Quick Start

Write a concise note after finishing work in unfamiliar areas and read relevant notes before starting the next task.

Frequently Asked Questions about session-memory

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

FAQPage Schema
How do I retain knowledge across different coding sessions?

To retain knowledge across coding sessions, you can use a cross-session memory system that writes structured notes after exploring unfamiliar code and reads them before starting new tasks. This captures experiential knowledge in project-level and cross-project storage.

How does cross-session note tracking work for recurring tasks?

Cross-session note tracking works by applying a dual-storage approach with structured templates containing Key Facts, Gotchas, and Patterns. It automatically logs substantive sessions to a dedicated memory file, ensuring knowledge persists for future decisions.

What is the best way to document unfamiliar code exploration for future reference?

The best way to document unfamiliar code exploration is writing structured notes immediately after finishing work. Use a defined template capturing Key Facts, Gotchas, Patterns, and Related Files, storing them in project-level or cross-project memory directories.

When should I write and read notes for cross-project learning?

You should write notes after exploring unfamiliar code areas or completing recurring tasks, and read relevant notes before starting new work. This ensures experiential knowledge from previous sessions informs and guides your future decisions.

Can I use project-level notes with my existing automation workflow?

Yes, project-level notes integrate with your automation workflow by storing structured learnings in a dedicated project directory. These notes are specifically designed for agent consumption, not human documentation, to automate and improve recurring task performance.

Does cross-session memory require any external dependencies or frameworks?

No, cross-session memory requires no external dependencies or frameworks. It operates independently using a dual-storage approach with project-level and cross-project notes, applying structured templates and defined read/write rules to ensure knowledge consistency.