How do I install the Attic Sweep skill?

Run npx skillmds@latest add nishikantaray/attic-sweep-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Attic Sweep safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Attic Sweep?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Attic Sweep free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published Attic Sweep?

NishikantaRay (@nishikantaray) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Attic Sweep by nishikantaray — Agent Skill

Name: Attic Sweep
Author: NishikantaRay

Attic Sweep

Save the state of the current session into the attic before context is lost: the current plan, open questions, in-progress work, and any finding not yet stashed. Use right before /compact or /clear, at the end of a session, or when the user says "save state", "wrap up", "before compact", "checkpoint", "context is getting long", "summarise what we've done so far", "where are we", or "recap the session". A request to recap session progress IS a sweep: give the recap and persist it in the same pass.

NishikantaRay Updated Sep 17, 2026

File contents

Sweep the session into the attic

First, in the same shell command as anything below, locate the script:

ATTIC_JS=$(ls -d "${CODEX_HOME:-$HOME/.codex}"/plugins/cache/attic/attic/*/skills/attic/scripts/attic.js "${CODEX_HOME:-$HOME/.codex}"/skills/attic/scripts/attic.js "$HOME"/.agents/skills/attic/scripts/attic.js .agents/skills/attic/scripts/attic.js 2>/dev/null | sort -V | tail -1)

Goal: after this runs, a fresh session that reads only .attic/INDEX.md could continue the work.

Pipeline:

Collect. Review the conversation for anything not yet stashed: findings, decisions and why, the current plan and what is done, open questions, and in-progress state (files being edited, failing tests, commands to rerun).
Dedupe. Run the index and drop anything already covered. Append to an existing item where there is genuinely new detail.

node "$ATTIC_JS" index

Write. One stash per finding or decision, following /attic-stash. Then one session item, using templates/session.md as the shape:

node "$ATTIC_JS" stash \
  --slug session-$(date +%F) --kind plan --title "Session $(date +%F)" \
  --hook "<what this session is doing, one line>" --body-file <tmpfile>

Verify.

node "$ATTIC_JS" validate

Fix anything it reports before finishing. 5. Report. List the handles written, one per line, then a single line: "Safe to /compact."

Copy commands, paths and errors verbatim. No secrets.

---name: attic-sweep-2description: Save the state of the current session into the attic before context is lost: the current plan, open questions, in-progress work, and any finding not yet stashed. Use right before /compact or /clear, at the end of a session, or when the user says "save state", "wrap up", "before compact", "checkpoint", "context is getting long", "summarise what we've done so far", "where are we", or "recap the session". A request to recap session progress IS a sweep: give the recap and persist it in the same pass.license: MIT---# Sweep the session into the atticFirst, in the same shell command as anything below, locate the script:```bashATTIC_JS=$(ls -d "${CODEX_HOME:-$HOME/.codex}"/plugins/cache/attic/attic/*/skills/attic/scripts/attic.js "${CODEX_HOME:-$HOME/.codex}"/skills/attic/scripts/attic.js "$HOME"/.agents/skills/attic/scripts/attic.js .agents/skills/attic/scripts/attic.js 2>/dev/null | sort -V | tail -1)```Goal: after this runs, a fresh session that reads only `.attic/INDEX.md`could continue the work.Pipeline:1. **Collect.** Review the conversation for anything not yet stashed: findings, decisions and why, the current plan and what is done, open questions, and in-progress state (files being edited, failing tests, commands to rerun).2. **Dedupe.** Run the index and drop anything already covered. Append to an existing item where there is genuinely new detail.```bashnode "$ATTIC_JS" index```3. **Write.** One stash per finding or decision, following `/attic-stash`. Then one session item, using `templates/session.md` as the shape:```bashnode "$ATTIC_JS" stash \ --slug session-$(date +%F) --kind plan --title "Session $(date +%F)" \ --hook "<what this session is doing, one line>" --body-file <tmpfile>```4. **Verify.**```bashnode "$ATTIC_JS" validate``` Fix anything it reports before finishing.5. **Report.** List the handles written, one per line, then a single line: "Safe to /compact."Copy commands, paths and errors verbatim. No secrets.

Frequently asked questions