memory-manager_skill

This skill optimizes agent memory usage, manages context windows, and archives conversations to improve recall and responsiveness.
  • TypeScript

6

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill dexploarer/hyper-forge --skill memory-manager

  • SKILL.md2.9 KB

Overview

This skill manages elizaOS agent memory, conversation history, and context windows to keep agents responsive and relevant. It provides pruning strategies, context-window tuning, and tools for archiving and consolidating important facts. The goal is to prevent context overload while preserving high-value long-term information.

How this skill works

The skill inspects short-term, long-term, and knowledge memory types and applies configurable operations: create, retrieve, search, update, and delete. It runs pruning routines (time-based and size-based), applies decay models for temporal relevance, and ranks memories by importance and recency. It also exposes monitoring hooks and embedding-based semantic search for efficient retrieval.

When to use it

  • When conversation context grows beyond model limits
  • Before sending prompts to ensure only relevant memories are included
  • To archive or consolidate long-lived user facts
  • When memory store costs or latency increase
  • To enforce data retention or compliance policies

Best practices

  • Define clear short-term vs long-term memory policies and limits
  • Score memories for importance and last-access to guide pruning
  • Use time-based decay to lower relevance of old transient items
  • Batch memory operations to reduce I/O and cost
  • Index and embed memories for semantic search and fast retrieval
  • Monitor memory growth and automate scheduled pruning

Example use cases

  • Trim a game-dev chat history to the most relevant 50 items before generating assets
  • Automatically archive completed design conversations into long-term storage with importance tags
  • Prune low-importance memories older than 30 days to control storage and context window size
  • Consolidate repeated user preferences into a single high-importance long-term memory
  • Run periodic audits that report memory count, average age, and top-k important memories

FAQ

Time-based pruning removes memories older than a cutoff, often filtered by low importance. Size-based pruning enforces a cap by keeping the most important and recent items and deleting the rest.

How can I preserve critical facts while pruning?

Assign importance metadata and consolidate duplicates into a single canonical memory; mark those as persistent or exempt from automated pruning.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational
memory-manager skill by dexploarer/hyper-forge | VeilStrat