meow:memory

Capture session learnings into memory/lessons.md and memory/patterns.json.

14|2|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/ngocsangyem/MeowKit --skill meow-memory
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: meow:memory
Source: https://github.com/ngocsangyem/MeowKit/tree/main/.claude/skills/meow%3Amemory
Command: npx skills add https://github.com/ngocsangyem/MeowKit --skill meow-memory

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Capture and persist session learnings to enable cross-session memory for MeowKit workflows.

Core Features & Use Cases

  • Session capture: record decisions, patterns, and failures after each session.
  • Pattern consolidation: track frequencies and surface recurring insights.
  • Cost tracking and budgeting hooks across sessions.

Quick Start

End-of-session save enables memory reuse for future analyses and improvements.

Frequently Asked Questions about meow:memory

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

FAQPage Schema
How do I persist session learnings across multiple workflow runs?

You can persist session learnings by capturing decisions, patterns, and failures at the end of each run. The system stores these entries in memory files to enable cross-session memory and surface insights for future workflows.

What is the best way to track recurring patterns and frequency in session memory?

Tracking recurring patterns in session memory involves recording insights and updating their frequency and lastSeen values. This pattern consolidation surfaces recurring insights automatically for future review and analysis.

How does cross-session memory work for cost tracking and budgeting?

Cross-session memory for cost tracking works by capturing session data at the end of each run and storing it in structured files. This provides hooks for budgeting and allows you to review cost patterns across previous sessions.

Can I use markdown and JSON files for storing session decisions and failures?

Yes, you can store session decisions and failures using markdown and JSON files. The system specifically writes entries to lessons.md for text records and patterns.json for structured frequency tracking and consolidation.

When do I need to save session memory for future analysis?

You need to save session memory at the end of each workflow run. Capturing this data at the end of a session ensures that decisions and failures are available to surface as insights for future analyses and improvements.

Do I need any dependencies to enable cross-session memory persistence?

No external dependencies are required to enable cross-session memory persistence. The system operates independently to capture session learnings and store them directly in local memory files for future reference and cost tracking.