One-click install
npx skills add https://github.com/dotnet/maui-labs --skill nap-dotnet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nap
Source: https://github.com/dotnet/maui-labs/tree/main/src/Comet/.copilot/skills/nap
Command: npx skills add https://github.com/dotnet/maui-labs --skill nap-dotnet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill fixes context bloat by compressing and pruning stored agent histories so your workspace stays small enough to continue productive work.

Core Features & Use Cases

  • History compression & archiving: Compresses agent histories, archives stale decisions, and retains usable summaries instead of everything.
  • Pruning noisy logs: Removes or prunes old logs and cleans orphaned inbox files to reduce redundant context.
  • Workspace cleanup triggers: Helps when history.md exceeds 15KB, when .squad/ exceeds 1MB, or after long-running sessions with many agent spawns.

Quick Start

Run squad nap with deep mode to aggressively reclaim context while preserving the most relevant recent 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 restore context budget in a multi-agent workspace?

Compress agent history by running a workspace cleanup that archives stale decisions, prunes old logs, and removes orphaned inbox files. This restores your context budget by shrinking oversized history.md files and .squad/ directories to practical sizes.

When should I prune logs and clean up agent workspace history?

Prune logs and clean agent workspace history when history.md exceeds 15KB, when .squad/ directories exceed 1MB, or after long-running sessions with many agent spawns. These triggers enforce context hygiene and prevent workspace bloat from degrading performance.

Can I dry run history compression before deleting agent logs and archived decisions?

Yes, you can dry run history compression to preview reclaimed context before executing. Dry-run mode shows what logs, orphaned inbox files, and stale decisions will be pruned or archived, while deep execution mode aggressively compresses and deletes the data.

What is the best way to clean orphaned inbox files and archive stale decisions in long-running sessions?

The best way to clean orphaned inbox files and archive stale decisions is using deep execution mode. It aggressively compresses histories, prunes old logs, and retains usable summaries instead of everything, restoring context budget for continued productive work.

Does multi-agent fan-out history compression retain recent state and usable summaries?

Multi-agent fan-out history compression retains usable summaries of recent state instead of deleting everything. It archives stale decisions and prunes old logs to reduce redundant context while preserving the most relevant recent state for ongoing sessions.

Why does my .squad directory exceed practical size thresholds after spawning many agents?

Your .squad directory exceeds practical size thresholds because long-running sessions with many agent spawns accumulate history files, logs, and orphaned inbox files. Context hygiene compression enforces triggers around .squad/ size and history.md to reclaim the oversized workspace.