memory-store

Store knowledge, entries, memories, and error patterns in the Worklog database.

Updated Dec 13, 2025

Search Tags:#context #memory #persistence #cross-session #knowledge-base #worklog

Ready to run

npx skills add https://github.com/gaurangrshah/gsc-plugins --skill memory-store

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: memory-store
Source: https://github.com/gaurangrshah/gsc-plugins/tree/main/plugins/worklog/skills/memory-store
Command: npx skills add https://github.com/gaurangrshah/gsc-plugins --skill memory-store

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Stores cross-session knowledge and contextual memory for the Worklog plugin, enabling information to survive restarts and task switches.

Core Features & Use Cases

Persist reusable learnings in knowledge_base for quick reference.
Save work entries, memories, and error patterns to maintain context across tasks.
Example: capture debugging notes and decisions so future sessions resume with context.

Quick Start

Store an example knowledge item to the worklog database to make it available across sessions.

Frequently Asked Questions about memory-store

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

FAQPage Schema

How do I persist context and memory across sessions for long-running tasks?▼

Cross-session memory persistence is achieved by storing knowledge, entries, and error patterns in a structured database. This ensures contextual data survives restarts and task switches so future sessions can resume with prior decisions intact.

What is the best way to save debugging notes and decisions for future reference?▼

Saving debugging notes involves writing reusable learnings and error patterns to a knowledge base. This allows you to maintain work entries and decision history that can be quickly referenced when resuming complex workflows.

Does cross-session knowledge persistence work with both SQLite and PostgreSQL backends?▼

Yes, cross-session knowledge persistence supports both SQLite and PostgreSQL backends. You can configure either database system to store structured worklog data depending on your environment's scale and infrastructure requirements.

Do I need the Worklog plugin to store context and memories across tasks?▼

Yes, the Worklog plugin is required to store context and memories across tasks. It must be properly configured before you can save work entries, knowledge items, and error patterns to the underlying database.

Can I capture error patterns and worklog entries to maintain context across task switches?▼

Capturing error patterns and worklog entries is fully supported to maintain context across task switches. Structured data is saved directly to the database, allowing interrupted workflows to resume with accurate historical context.

What are the limitations of using a knowledge base for cross-session persistence?▼

Cross-session persistence relies entirely on a configured database backend, meaning functionality is limited without the Worklog plugin. Data retrieval depends on database availability, and unstructured conversational context outside stored entries is not retained.