agentsclimarketplace

Agent memory systems

Skill newmindsgroup/ai-agent-skills-library/dist/skills/agent-memory-systems

Shared library of AI agent skills — works across Claude Code, Cursor, Codex, Windsurf, OpenCode, and Google Antigravity via a single universal installer.

Install
npx -y skills add newmindsgroup/ai-agent-skills-library --skill agent-memory-systems

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Memory is the cornerstone of intelligent agents. Without it, every

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

3.1 KB, 569 tokens by cl100k_base, as published. Nobody here has run it

Agent Memory Systems

Memory is the cornerstone of intelligent agents. Without it, every interaction starts from zero. This skill covers the architecture of agent memory: short-term (context window), long-term (vector stores), and the cognitive architectures that organize them.

Key insight: Memory isn't just storage - it's retrieval. A million stored facts mean nothing if you can't find the right one. Chunking, embedding, and retrieval strategies determine whether your agent remembers or forgets.

The field is fragmented with inconsistent terminology. We use the CoALA cognitive architecture framework: semantic memory (facts), episodic memory (experiences), and procedural memory (how-to knowledge).

When to Use

  • User mentions or implies: agent memory
  • User mentions or implies: long-term memory
  • User mentions or implies: memory systems
  • User mentions or implies: remember across sessions
  • User mentions or implies: memory retrieval
  • User mentions or implies: episodic memory
  • User mentions or implies: semantic memory
  • User mentions or implies: vector store
  • User mentions or implies: rag
  • User mentions or implies: langmem

Core Workflow

  1. Confirm the request matches this skill's trigger, scope, and risk profile.
  2. Use the topic map to identify the relevant pattern, checklist, or example before writing detailed guidance or code.
  3. Load references/full-guidance.md when implementation details, examples, anti-patterns, validation checks, or edge cases are needed.
  4. Apply only the relevant guidance instead of loading or repeating the entire reference by default.
  5. Verify the result against any validation checks, limitations, security notes, or platform constraints in the reference.

Topic Map

  • Principles
  • Capabilities
  • Scope
  • Tooling
  • Memory_frameworks
  • Vector_stores
  • Embedding_models
  • Patterns
  • Memory Type Architecture
  • LangMem Implementation
  • Memory Retrieval at Runtime
  • Vector Store Selection Pattern
  • Pinecone (Enterprise Scale)
  • Qdrant (Complex Filtering)
  • ChromaDB (Prototyping)
  • Chunking Strategy Pattern
  • Fixed-Size Chunking (Baseline)
  • Semantic Chunking (Better Quality)

Reference Map

  • references/full-guidance.md preserves the complete original guidance, including examples and detailed edge cases.

Limitations

  • Use this skill only when the task clearly matches the scope described above.
  • Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
  • Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Progressive Loading

Keep this SKILL.md as the compact routing and workflow entrypoint. Load the reference file only when the user task requires the deeper implementation material.

Gives 0 of the 12 instructions most memory context skills give in 569 tokens

Counted across 674 of the 847 authors here whose files we hold, read 2026-08-06

  • inform the user when setup is completein 21 of 674, across 6 files
  • confirm the draft with the user before writingin 21 of 674, across 6 files
  • update the agent skills block in place if it existsin 21 of 674, across 6 files
  • present findings to the userin 20 of 674, across 5 files
  • write the three docs files from seed templatesin 20 of 674, across 5 files
  • ask the user about each decision one at a timein 19 of 674, across 4 files
  • edit CLAUDE.md if it existsin 18 of 674, across 3 files
  • explore current repo statein 18 of 674, across 3 files
  • do not overwrite user edits to surrounding sectionsin 18 of 674, across 3 files
  • back up the original file before overwritingin 16 of 674, across 8 files
  • keep the memory index under 200 linesin 15 of 674
  • Provide actionable steps and verificationin 13 of 674, across 2 files

Said here and by no other author read

  • ask for clarification if required inputs are missing
  • confirm the request matches this skill
  • use the topic map to identify relevant patterns
  • load full guidance for implementation details
  • apply only the relevant guidance

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.