agentleFS
Sign inStart free
npownpow/claude-skills/nap/SKILL.md

nap

Skill4 starsChanged 6 months agoApache-2.0View on GitHub

Context compactor — prunes old sagaflow runs, archives stale memory files, compacts MEMORY.md indexes, compresses aimee journals. Like Squad's `squad nap` but for our Claude Code setup.

4 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 1 is distinctive, and 5 are very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When invoked, run the nap script:

    line 16
  2. Very specific:

    If the user says --dry-run or "dry run" or "what would it do": add --dry-run

    line 24
  3. Very specific:

    If the user says --deep or "deep" or "aggressive": add --deep

    line 25
  4. Very specific:

    If no flags specified: run with --dry-run first, show the report, then run for real

    line 26
  5. Very specific:

    Run with --dry-run first unless the user explicitly said to just do it

    line 37
  6. Very specific:

    If dry-run, ask once: "Run it for real?" — then execute without --dry-run

    line 39

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

nap

Compact Claude Code context state to free disk and reduce token load.

Usage

When invoked, run the nap script:

python3 ~/code/npow-dotfiles/scripts/nap.py [flags]

Flags from user args

  • If the user says --dry-run or "dry run" or "what would it do": add --dry-run
  • If the user says --deep or "deep" or "aggressive": add --deep
  • If no flags specified: run with --dry-run first, show the report, then run for real

What it does

  1. PRUNE — deletes sagaflow run dirs older than 7 days (3 with --deep)
  2. COMPACT — removes dead pointers from MEMORY.md index files
  3. ARCHIVE — moves memory files not touched in 30 days (14 with --deep) to archive/ subdirs
  4. COMPRESS — archives old aimee journal entries (>7 days or >50KB; >3 days or >20KB with --deep)

Workflow

  1. Run with --dry-run first unless the user explicitly said to just do it
  2. Show the report output to the user
  3. If dry-run, ask once: "Run it for real?" — then execute without --dry-run
  4. Show the final report

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free