session-to-memory

Extracts retention-worthy knowledge from session history and persists it to the active memory provider.

Updated Jul 11, 2026
One-click install
npx skills add https://github.com/danielsuguimoto/skills --skill session-to-memory-danielsuguimoto
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: session-to-memory
Source: https://github.com/danielsuguimoto/skills/tree/main/skills/session-to-memory
Command: npx skills add https://github.com/danielsuguimoto/skills --skill session-to-memory-danielsuguimoto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Valuable insights discovered during a work session — invariants, pitfalls, architectural decisions — are lost when the session ends. This Skill captures that hard-won knowledge and stores it in a persistent memory provider so future sessions and agents can reuse it. ## Core Features & Use Cases - Knowledge Extraction: Scans conversation history, tool outputs, and touched files to identify reusable, non-obvious facts that clear a strict write bar. - Dedupe and Structure: Checks existing memories before writing, edits overlapping entries, and organizes knowledge under stable slash-separated topic paths like pitfalls/<topic> or decisions/<topic>. - Provider-Based Persistence: Hands each write to the active memory-provider driver defined in <project-root>/docs/memory-providers.md, keeping storage mechanics decoupled. - Use Case: After a long debugging session that uncovered a non-obvious API rate-limit behavior, run this Skill to distill that finding into a memory entry so the next agent never rediscovers it the hard way. ## Quick Start Ask the agent to save what we learned this session to memory before wrapping up the task.

Frequently Asked Questions about session-to-memory

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

FAQPage Schema
How do I save session learnings to persistent memory?▼

Run the session-to-memory workflow at the end of a non-trivial session. It scans conversation history and tool outputs, filters candidates against a write bar, dedupes against existing memories, and persists distilled entries through the active memory provider.

What knowledge is worth extracting from a coding session?▼

Keep non-obvious invariants, project conventions, pitfalls that required real investigation, architectural decisions with lasting rationale, and external API quirks. Drop anything trivially greppable from the codebase, one-off typos, or reversible preferences.

When should I not run session memory extraction?▼

Skip it for trivial sessions such as a single command, a one-line answer, or work with no real investigation. If nothing clears the write bar defined by the memory-usage skill, the correct behavior is to report that and stop.

What happens if the memory provider is unavailable?▼

The workflow reports BLOCKED and stops immediately. It never invents a fallback store or writes to an alternative location, since persistence ownership belongs to the configured memory-provider driver.

Does session memory extraction store conversation history?▼

No. It never persists conversation state, task progress, session scratchpads, secrets, credentials, or PII. Only distilled, reusable knowledge is stored, with file:line citations instead of duplicated code content.