memory-scriber

Capture conversation essence into the active host's memory directory.

Updated Apr 26, 2026
One-click install
npx skills add https://github.com/kennykankush/skillpack --skill memory-scriber
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: memory-scriber
Source: https://github.com/kennykankush/skillpack/tree/main/plugins/workbench/skills/memory-scriber
Command: npx skills add https://github.com/kennykankush/skillpack --skill memory-scriber

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Capture a conversation's essence into the active host's memory directory, and recall it back like a colleague - not a database. Use at the tail end of a substantive session ("log this", "memory-scribe this"), progressively during one ("scribe as we go", "checkpoint this"), or in reverse when the user asks to recall or pick up the thread.

Core Features & Use Cases

  • End-to-end memory capture: log key decisions, insights, and context as the session evolves or at its end.
  • Cross-host recall: retrieve relevant memories across Codex and Claude Code runtimes with minimal friction.
  • Project-scoped continuity: link memories to the active project slug and surface durable pointers for future sessions.

Quick Start

Log this session to memory now using memory-scriber and recall it later when needed.

Frequently Asked Questions about memory-scriber

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

FAQPage Schema
How do I save and recall Claude Code session context across different runs?

Capture and recall session context across Claude Code runs by logging key decisions into the active host's memory directory. You can trigger tail-end logging or progressive scribing during a session to ensure future continuity.

Can I use Codex to retrieve conversation memories logged from a different runtime?

Cross-host recall allows you to retrieve conversation memories across Codex and Claude Code runtimes. It safely handles project-scoped memory references and maintains consistent memory indexing for minimal friction.

What is the best way to log coding session decisions for future reference?

The best way to log session decisions is using progressive scribing or tail-end logging. This captures the conversation's essence into a memory directory, linking memories to the active project slug for future sessions.

Does memory-scriber require any external dependencies to store conversation logs?

Memory-scriber requires no external dependencies to store conversation logs. It operates independently to capture the conversation's essence and store it in the active host's memory directory for later recall.

When should I use progressive scribing instead of tail-end logging for session memory?

Use progressive scribing during a substantive session to checkpoint context as it evolves, rather than tail-end logging which captures the full conversation essence only at the session's conclusion.

Why are my recalled conversation memories not linking to the correct project scope?

Recalled memories link to the correct project scope through safe handling of project-scoped memory references and consistent memory indexing. Ensure your active project slug is correctly configured before logging.