Menu

Individual skill

archive-strategy

0upvotes

Design the archive layer that keeps current workspaces lean without losing history — what moves, when, to where, findable-by-search, with the project-close ritual that makes archiving automatic instead of aspirational. Use when asked set up an archiving system, our workspace is drowning in old projects, when should things get archived, or make history findable without cluttering today. Produces the archive triggers, the destination structure, the findability rules, and the close-out ritual.

skills/archive-strategy/SKILL.md

Read pinned source

Source commit f7c90bc09ee05dc25cf257bdb1826f2c2552c2cb

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,539
Repository last updated
Nov 10, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Archive Strategy Skill

Workspaces drown not in bad files but in *finished* ones — closed projects, past years, shipped versions — all cluttering the space where current work lives, because "archive" was never defined as an action with a trigger. A working archive strategy answers four questions structurally: *when* does something move (triggers, not judgment calls), *where* (a parallel dated structure, not a junk room), *how is it found* (search + a skeleton index, not browsing), and *who moves it* (the close-out ritual, so archiving happens at natural endings instead of never).

## What This Skill Produces

- **The triggers** — the events that move material to archive automatically: project close, year end, version supersession, person departure
- **The destination structure** — `_archive/[year]/[original-path]` mirroring, so provenance survives the move
- **The findability layer** — search-first retrieval + the one-page archive index for the things search misses
- **The close-out ritual** — the 20-minute end-of-project checklist where archiving actually happens

## Required Inputs

Ask for these if not provided:
Back to top