What do I need to use Archive Strategy?

The workspace(s); The natural endings; The retrieval reality; Retention constraints.

Is Archive Strategy free to use?

Yes — run it free in the browser playground (no API key needed for the sponsored trial, or bring any provider key), or install it into Claude Code, Cursor, ChatGPT and more via npx pm-claude-skills. MIT-licensed and open source.

Archive Strategy

Q: How do I know the Archive Strategy output is good?

The skill verifies itself against its own quality checks: Every trigger names a real event and a mover; The archive mirrors original paths under a year layer; Retrieval is search + skeleton index — no archive taxonomy project; The ritual is attached to an existing close process with an owner.

🔵 Stable🕐 updated 2026-07-19 🔷 SkillSpec L3 pm-cowork

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.

▶ Run it free — no key needed 📝 Grade your existing draft View SKILL.md ↗

What to give it

▸The workspace(s) — drive, project tool, wiki, or all three; each gets the same triggers, platform-appropriate mechanics

▸The natural endings — what "closed" looks like here (shipped, signed-off, renewed, year-end); triggers attach to real events the team already recognizes

▸The retrieval reality — how often archived material actually gets fetched, and by whom; findability effort scales to real demand, not imagined

▸Retention constraints — anything with keep-periods or destruction dates ([document-retention-map](../document-retention-map/SKILL.md) rules ride along into the archive)

✅ The bar it holds itself to

Every skill in this library self-verifies — these are this skill's own quality checks, straight from its definition.

✓Every trigger names a real event and a mover

✓The archive mirrors original paths under a year layer

✓Retrieval is search + skeleton index — no archive taxonomy project

✓The ritual is attached to an existing close process with an owner

✓The current workspace visibly shrank — the strategy's actual success metric

⚠️ What it refuses to do

Do not archive by mood — triggerless archiving is a euphemism for never

Do not flatten paths into a dump — provenance is findability

Do not reorganize while archiving — the move is a move; improving history is a separate (usually skippable) project

Do not build archive taxonomy — search plus ten index lines outperforms it at 5% of the cost

Do not let archives exempt themselves from retention rules — destruction dates ride along with the files

Install

npx pm-claude-skills add --agent claude   # or codex · cursor · gemini · hermes
# or one-line MCP (every skill, any client):
claude mcp add pm-skills -- npx -y pm-claude-skills-mcp

Related skills

🔌 Embed this skill

Drop this on your blog, docs, or site — it renders a "Run this skill" card:

<div data-pm-skill="archive-strategy"></div>
<script src="https://mohitagw15856.github.io/pm-claude-skills/embed.js" async></script>

💬 Discussion

Archive Strategy is one of 750 open-source professional AI agent skills — all SkillSpec L3. Try them all in the browser · ⭐ Star on GitHub · Browse the full catalog