nap

Compress agent history files and prune stale logs in the .squad/ directory.

1|Updated Dec 23, 2025
One-click install
npx skills add https://github.com/jonnymuir/Umbraco.Prism --skill nap-jonnymuir
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nap
Source: https://github.com/jonnymuir/Umbraco.Prism/tree/main/.copilot/skills/nap
Command: npx skills add https://github.com/jonnymuir/Umbraco.Prism --skill nap-jonnymuir

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the accumulation of excessive context and clutter within the .squad/ directory, which can degrade agent performance and consume unnecessary memory.

Core Features & Use Cases

  • Context Compression: Shrinks agent history files to maintain a lean context window.
  • Cleanup & Archiving: Prunes old logs and archives stale decisions to keep the workspace organized.
  • Use Case: Before initiating a complex, multi-agent task, use this Skill to clear out historical noise and ensure the agents have a clean, relevant state to work from.

Quick Start

Invoke the nap skill to prune old logs and compress agent history files in the current workspace.

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 files to optimize context window hygiene?

To optimize context window hygiene, compress agent history files by invoking an automated cleanup process. This shrinks accumulated context data within the .squad/ directory, preventing memory degradation and maintaining a lean workspace state for active development sessions.

What is the best way to prune stale logs and archive old decisions in a multi-agent workflow?

Pruning stale logs and archiving old decisions in a multi-agent workflow is best handled by automated workspace maintenance. This process clears historical noise and organizes cluttered directories, ensuring agents operate from a clean, relevant state before complex tasks.

Does automated context cleanup require manual file intervention for long-running development sessions?

Automated context cleanup does not require manual file intervention for long-running development sessions. The process automatically compresses agent history and prunes stale log files, satisfying workspace maintenance requirements without manual effort.

Why does agent performance degrade when the .squad/ directory accumulates excessive context?

Agent performance degrades when the .squad/ directory accumulates excessive context because the clutter consumes unnecessary memory and bloats the context window. Pruning stale logs and compressing history mitigates this degradation.

When do I need to archive stale decisions and clear historical noise before starting a task?

You need to archive stale decisions and clear historical noise before initiating complex, multi-agent tasks. This ensures agents have a clean, relevant state to work from, preventing accumulated historical clutter from degrading performance.