tiered-memory

Organizes agent context into hot, cold, and wiki memory tiers to reduce spawn payload size.

1|Updated Jul 7, 2026
One-click install
npx skills add https://github.com/seiggy/maf-copilot-studio-demo --skill tiered-memory-seiggy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tiered-memory
Source: https://github.com/seiggy/maf-copilot-studio-demo/tree/main/.squad/templates/skills/tiered-memory
Command: npx skills add https://github.com/seiggy/maf-copilot-studio-demo --skill tiered-memory-seiggy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Squad agents load their full context history on every spawn, producing 34–74KB payloads where 82–96% is stale noise. This Skill defines a three-tier memory model that cuts context size by 20–55% per spawn by loading only what the current task needs. ## Core Features & Use Cases - Three-Tier Memory Model: Hot tier (2–4KB current session context, always loaded), Cold tier (8–12KB summarized cross-session history, loaded on demand), and Wiki tier (durable structured knowledge like ADRs and conventions, loaded selectively). - Spawn Template Pattern: Provides a ready-to-use spawn prompt template that defaults to Hot-only loading, with --include-cold and --include-wiki flags for tasks needing history or domain knowledge. - Scribe Integration: Defines how the Scribe agent automates tier promotion, compressing Hot to Cold at session end and promoting Cold to Wiki after a 30-day rolling window. - Use Case: When resuming interrupted work, spawn an agent with Hot context plus the Cold summary file instead of replaying full transcripts, cutting token usage while preserving relevant decisions. ## Quick Start Spawn an agent using the tiered-memory template with only the Hot context section filled in, and add the Cold or Wiki sections only when the task requires prior history or domain reference docs.

Frequently Asked Questions about tiered-memory

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

FAQPage Schema
How do I reduce agent context size when spawning AI agents?

Split agent memory into tiers: always load a small hot tier with current session context (2–4KB), and load summarized cold history or wiki reference docs only when the task needs them. Production measurements show 20–55% context reduction per spawn with hot-only loading.

What is a tiered memory model for AI agents?

A tiered memory model separates agent context into a hot tier for current session state, a cold tier for summarized cross-session history with a 30-day TTL, and a wiki tier for durable structured knowledge like ADRs and conventions. Each tier has its own load policy and lifetime.

When should I load cold memory versus wiki memory?

Load cold memory when resuming interrupted work or debugging recurring issues, since it holds summarized past sessions. Load wiki memory when implementing against a spec or onboarding to an unfamiliar subsystem, since it holds stable decisions and conventions rather than history.

How does memory promotion between tiers work?

A coordinator agent (Scribe) compresses hot context into a cold summary at session end, keeping roughly 10% of session verbosity. After 30 days, cold entries that have aged into stable knowledge are promoted to the wiki tier, and agents can also request mid-session wiki writes.

What are the limitations of hot-only context loading?

Hot-only loading drops access to prior session history and durable domain knowledge, so tasks that depend on past decisions or specs can stall. Mitigate this by adding cold or wiki sections selectively, which adds roughly 2–12KB depending on the tier.