nap

Name: nap
Availability: InStock
Author: deduva

Compress agent histories and prune old logs to reclaim context window budget.

1|Updated Apr 18, 2026

Search Tags:#context #history #compression #archiving #pruning #squad #nap

Ready to run

npx skills add https://github.com/DeDuva/squad --skill nap-deduva

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: nap
Source: https://github.com/DeDuva/squad/tree/main/packages/squad-sdk/templates/skills/nap
Command: npx skills add https://github.com/DeDuva/squad --skill nap-deduva

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reclaims context window budget by compressing agent histories, pruning old logs, archiving stale decisions, and cleaning orphaned inbox files.

Core Features & Use Cases

Compresses agent histories to reclaim context window space.
Prunes old logs and archives stale decisions to keep the project lean.
Cleans up orphaned inbox files to prevent clutter and confusion.

Quick Start

Run squad nap to compress history, prune logs, and archive the .squad state.

Frequently Asked Questions about nap

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

FAQPage Schema

How do I compress agent history to reclaim context window budget?▼

To compress agent history and reclaim context window budget, you can run a command that applies deterministic operations to prune old logs, archive stale decisions, and clean orphaned inbox files. This keeps the project lean during heavy fan-out work.

What is the best way to prune old logs and archive stale decisions in a squad state?▼

Archiving stale decisions and pruning old logs in a squad state is handled by deterministic history compression. Running a dedicated nap command cleans the .squad storage, preventing clutter and confusion while freeing up context window space.

When should I clean up orphaned inbox files during heavy fan-out work?▼

You should clean up orphaned inbox files when .squad storage grows beyond limits or after long sessions. Reclaiming context window budget by compressing agent histories prevents clutter and confusion during heavy fan-out work.

Does history compression work without external dependencies?▼

Yes, history compression works without external dependencies because it applies deterministic operations directly to the local .squad state. It prunes logs, archives decisions, and cleans inbox files to reclaim context window budget autonomously.

How do I reclaim context window space after a long agent session?▼

To reclaim context window space after a long agent session, compress agent histories to prune old logs and archive stale decisions. Running a single command cleans orphaned inbox files and reduces the .squad storage footprint.