gentleman-programming/engram

engram-memory-protocol

Persistent memory discipline for Engram contributors.

View source

How to use

  1. Copy the installation command and review the source package before installing it in your own agent environment.
  2. Check the source document for required tools, credentials and supported hosts.
  3. Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/gentleman-programming/engram --skill engram-memory-protocol

Before you start

  • Installation does not include a model subscription, API allowance or permission to access your files.
  • Repository stars and installation counts describe activity, not an independent quality or security test.
Original skill document

Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.

When to Use

Use this skill when:

  • Making architecture or implementation decisions
  • Fixing bugs with non-obvious root causes
  • Discovering patterns, gotchas, or user preferences
  • Closing a session or after compaction

Save Rules

Call mem_save immediately after:

  • decision
  • bugfix
  • pattern/discovery
  • config/preference changes

Use structured content:

  • What
  • Why
  • Where
  • Learned

Use stable topic_key for evolving topics.


Search Rules

  • On recall requests: mem_context first, then mem_search.
  • Before similar work: run proactive mem_search.
  • On first message: if user references the project, a feature, or a problem, call mem_search with their keywords before responding.

Session Close Rules

Before saying done/listo:

  1. Call mem_session_summary.
  2. Include goal, discoveries, accomplished, next steps, relevant files.

After compaction:

  1. Save summary first.
  2. Recover context.
  3. Continue work.

Delivery Guarantee

Memory operations are internal bookkeeping, never the user-facing answer. Complete required memory work before composing the completed-task reply; send the complete answer as the final message of the turn with no later tool calls. If memory work fails or needs follow-up, still send the answer.

Related by task

from this repository

More skills

All skills