gaia-compact

Preserve six session context categories before invoking the /compact operation.

3|1|Updated Nov 10, 2025
One-click install
npx skills add https://github.com/metraton/gaia --skill gaia-compact
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gaia-compact
Source: https://github.com/metraton/gaia/tree/main/skills/gaia-compact
Command: npx skills add https://github.com/metraton/gaia --skill gaia-compact

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Preserving critical session context and decisions during compaction solves the problem of lossy summaries.

Core Features & Use Cases

  • Maintains six preservation categories: DECISIONS, COMPONENTS, OPEN ITEMS, FILE MAP, KEY FINDINGS, NEXT STEPS, so context survives summarization.
  • Builds a combined preservation prompt from user instructions and base policy, ensuring fidelity and clarity.
  • Verifies and surfaces any in-flight persistence-critical work before applying the compaction to prevent data loss.

Quick Start

Ask Gaia to compact the current session to preserve decisions, components, open items, file map, key findings, and next steps.

Frequently Asked Questions about gaia-compact

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

FAQPage Schema
How do I preserve session context when compacting an agent orchestration workflow?

To preserve session context during compaction, enforce a preservation contract that retains six categories: DECISIONS, COMPONENTS, OPEN ITEMS, FILE MAP, KEY FINDINGS, and NEXT STEPS. This prevents lossy summaries in multi-step workflows.

Why does session compaction lose critical decisions and open items?

Session compaction loses critical decisions because standard summarization is lossy. A preservation contract solves this by building a combined prompt from base policy and verifying persistence-critical work before applying compaction.

What's the best way to prevent data loss during a compact operation?

The best way to prevent data loss during a compact operation is to verify and surface any in-flight persistence-critical work before invoking compaction, ensuring ongoing planning sessions and complex agent orchestration retain essential context.

How do I maintain a file map and key findings when summarizing a planning session?

To maintain a file map and key findings when summarizing a planning session, apply a preservation policy that enforces retaining six specific categories, building a combined prompt from user instructions and base policy for fidelity.

Does compaction work with complex multi-step agent workflows?

Yes, compaction works with complex multi-step agent workflows by enforcing a preservation contract that safeguards DECISIONS, COMPONENTS, OPEN ITEMS, FILE MAP, KEY FINDINGS, and NEXT STEPS before the session is summarized.

When should I not use standard summarization for ongoing sessions?

You should not use standard summarization for ongoing sessions when in-flight persistence-critical work exists, as it causes lossy summaries; instead, verify context and enforce preservation categories before compacting.