cognitive-memory

Preserve context across Claude Code sessions with semantic memory recall.

Updated Feb 15, 2026
One-click install
npx skills add https://github.com/jsschrstrcks1/manateecreeksheep --skill cognitive-memory-jsschrstrcks1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cognitive-memory
Source: https://github.com/jsschrstrcks1/manateecreeksheep/tree/main/.claude/skills/cognitive-memory
Command: npx skills add https://github.com/jsschrstrcks1/manateecreeksheep --skill cognitive-memory-jsschrstrcks1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Persistent context across Claude Code sessions supports continuity, semantic recall, and reasoning over long-running tasks.

Core Features & Use Cases

  • Semantic recall via TF-IDF search to surface relevant memories
  • Memory versioning and knowledge-graph linking to resolve contradictions
  • Domain-scoped memory store with decay-based consolidation for long-running projects
  • Cross-session context maintenance for consistent guidance and decision-making

Quick Start

Recall my recent memories about flock parasite resistance across sessions.

Frequently Asked Questions about cognitive-memory

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

FAQPage Schema
How do I maintain persistent memory across Claude Code sessions?

A local domain-scoped memory store preserves context across Claude Code sessions, enabling cross-repository knowledge retention and continuity for long-running tasks.

What is semantic recall and how does it work for development context?

Semantic recall uses TF-IDF search to surface relevant memories from the local store, allowing retrieval of development, planning, and debugging context across sessions.

How do I resolve contradictions in memory versioning during debugging?

Memory versioning and knowledge-graph linking resolve contradictions by tracking changes over time and connecting related concepts, ensuring consistent guidance across sessions.

Does cross-repository knowledge retention work with decay-based consolidation?

Cross-repository knowledge retention uses decay-based consolidation to manage the local domain-scoped store, automatically prioritizing relevant long-running project context over stale data.

Can I recall specific memories from previous sessions without manual searching?

You can recall specific memories from previous sessions using semantic search queries, which trigger the defined operations interface to surface relevant stored context automatically.

When should I use a knowledge-graph linked memory store for software engineering?

A knowledge-graph linked memory store is needed for long-running tasks requiring cross-session context maintenance, contradiction resolution, and consistent guidance across repositories.