tiered-memory

Implement three-tier Hot, Cold, and Wiki memory for Squad agents.

619|188|Updated Jul 4, 2024
One-click install
npx skills add https://github.com/CommunityToolkit/Aspire --skill tiered-memory-communitytoolkit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tiered-memory
Source: https://github.com/CommunityToolkit/Aspire/tree/main/examples/squad/CommunityToolkit.Aspire.Hosting.Squad.AppHost/dev-squad/.squad/templates/skills/tiered-memory
Command: npx skills add https://github.com/CommunityToolkit/Aspire --skill tiered-memory-communitytoolkit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires Scribe, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Squad agents loading full context history for every spawn results in unnecessary "old noise" and large payloads, leading to inefficiencies and increased computational overhead.

Core Features & Use Cases

  • Three-Tier Memory Model: Hot, Cold, and Wiki tiers for context management, reducing payload size.
  • Context Reduction: Achieve 20-55% context reduction per spawn.
  • Use Case: For a Squad agent handling complex tasks with large context histories, this skill can help reduce computational load and improve performance.

Quick Start

Use the tiered-memory skill to spawn a Squad agent with Hot, Cold, and Wiki memory tiers enabled.

Frequently Asked Questions about tiered-memory

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

FAQPage Schema
How do I reduce context payload size for Squad agents?

Reduce context payload size for Squad agents by implementing a three-tier memory model that separates data into Hot, Cold, and Wiki tiers, achieving 20-55% context reduction per spawn. This eliminates unnecessary old noise from full history loading.

How does tiered memory management improve agent performance?

Tiered memory management improves performance by supporting on-demand loading of Cold and Wiki memory tiers, which prevents loading full context history for every spawn and significantly reduces computational overhead.

Do I need Scribe to manage memory tiers for Squad agents?

Yes, you need the Scribe dependency to act as a memory coordinator for managing Hot, Cold, and Wiki memory tiers, which is required to enable on-demand loading and reduce payload sizes.

Why does loading full context history increase computational overhead for agents?

Loading full context history increases computational overhead because it results in large payloads and unnecessary old noise for every spawn, which a three-tier memory model solves by shrinking payload size by 20-55%.

What is the best way to optimize context for complex Squad agent tasks?

The best way to optimize context for complex Squad agent tasks is enabling a three-tier memory model that achieves 20-55% context reduction per spawn, significantly lowering the computational load while handling large context histories.