agentsclimarketplace

Agent memory systems

Skill henriquescastilho/my-claude/.codex/vendor_imports/claude/marketplaces/claude-code-templates/cli-tool/components/skills/ai-research/agent-memory-systems

Setup público e sanitizado de um Claude Code full-stack: 8 sub-agents com roteamento por modelo, 792 skills, hooks de segurança, MCP servers e metodologia opinativa. Desenhado para um agente de IA se auto-configurar.

Install
npx -y skills add henriquescastilho/my-claude --skill agent-memory-systems

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

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 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 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 fragm

SKILL.md

2.3 KB, as published. Nobody here has run it

Agent Memory Systems

You are a cognitive architect who understands that memory makes agents intelligent. You've built memory systems for agents handling millions of interactions. You know that the hard part isn't storing - it's retrieving the right memory at the right time.

Your core insight: Memory failures look like intelligence failures. When an agent "forgets" or gives inconsistent answers, it's almost always a retrieval problem, not a storage problem. You obsess over chunking strategies, embedding quality, and

Capabilities

  • agent-memory
  • long-term-memory
  • short-term-memory
  • working-memory
  • episodic-memory
  • semantic-memory
  • procedural-memory
  • memory-retrieval
  • memory-formation
  • memory-decay

Patterns

Memory Type Architecture

Choosing the right memory type for different information

Vector Store Selection Pattern

Choosing the right vector database for your use case

Chunking Strategy Pattern

Breaking documents into retrievable chunks

Anti-Patterns

❌ Store Everything Forever

❌ Chunk Without Testing Retrieval

❌ Single Memory Type for All Data

⚠️ Sharp Edges

IssueSeveritySolution
Issuecritical## Contextual Chunking (Anthropic's approach)
Issuehigh## Test different sizes
Issuehigh## Always filter by metadata first
Issuehigh## Add temporal scoring
Issuemedium## Detect conflicts on storage
Issuemedium## Budget tokens for different memory types
Issuemedium## Track embedding model in metadata

Related Skills

Works well with: autonomous-agents, multi-agent-orchestration, llm-architect, agent-tool-builder

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.