engramory

Store durable facts and project state in size-capped markdown notes.

139|9|Updated Jun 13, 2026
One-click install
npx skills add https://github.com/tinqiao-oss/engramory --skill engramory
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: engramory
Source: https://github.com/tinqiao-oss/engramory/tree/main
Command: npx skills add https://github.com/tinqiao-oss/engramory --skill engramory

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill solves the problem of fragmented, unmanaged agent memory by providing a strict, human-readable, and curated protocol for storing durable facts, project state, and behavioral agreements.

Core Features & Use Cases

  • Curated Memory: Uses a one-file-one-fact approach with a typed ontology (user, feedback, project, reference) to ensure memory remains actionable and clean.
  • Bounded Indexing: Implements a size-capped index that prevents context window overflow while ensuring critical information is always available.
  • Use Case: Maintain a consistent set of project-specific coding standards and user preferences across multiple sessions without relying on opaque, non-editable vector databases.

Quick Start

Use the engramory skill to initialize a new memory store in the current project directory and wire the discipline into your agent rules.

Frequently Asked Questions about engramory

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

FAQPage Schema
How do I maintain AI agent memory across multiple sessions without a vector database?

AI agent memory can persist across sessions using a file-based markdown protocol with a bounded index, storing durable facts and project state in atomic notes instead of an opaque vector database. This approach ensures persistent storage of user preferences and procedural feedback without external dependencies.

What is a curated memory protocol for AI agents and how does it work?

A curated memory protocol for AI agents enforces memory hygiene by using a one-file-one-fact approach with a typed ontology. It categorizes facts into user, feedback, project, and reference types, ensuring stored knowledge remains actionable and clean through strict curation discipline and size-capped index validation.

How do I prevent context window overflow when storing long-term agent memory?

Prevent context window overflow by implementing a size-capped index that bounds the volume of stored facts. This mechanism enforces memory hygiene through strict curation discipline, ensuring critical information is always available while preventing unbounded memory growth that exceeds context limits.

Can I use markdown files to store project-specific coding standards for my AI agent?

Yes, you can use markdown files to store project-specific coding standards. The protocol uses atomic markdown notes with a typed ontology, allowing you to maintain consistent behavioral agreements and project state across multiple sessions in a human-readable format.

What is the best way to manage fragmented agent memory and keep it editable?

The best way to manage fragmented agent memory is using a strict, human-readable protocol with atomic markdown notes. This approach solves unmanaged memory fragmentation by enforcing curation discipline and a bounded index, keeping stored facts editable and actionable without relying on opaque systems.

Why does my AI agent forget user preferences between different sessions?

AI agents forget user preferences between sessions when they lack a persistent long-term memory protocol. Implementing a file-based memory store with a bounded index and typed ontology ensures user preferences and behavioral agreements are durably stored and retrieved across multiple interactions.