Agent skill

Archive Strategy

by mohitagw15856 in mohitagw15856/pm-claude-skills

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…

MITAuto-check passed

Install Archive Strategy

skills CLI
$ npx skills add mohitagw15856/pm-claude-skills --skill archive-strategy -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install mohitagw15856/pm-claude-skills archive-strategy --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/archive-strategy .claude/skills/archive-strategy && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
archive-strategy
GitHub stars
1.4k
Token cost
~1.3k tokens
SKILL.md length
644 words
Files
1
Skills in repo
1,348
Repo updated
First seen
Licence
MIT

At a glance

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…

  • Works in 5 steps: Triggers beat judgment: "archive when… → Mirror the path, date the layer:… → Search-first, index-light: archives are… → …
  • Asked set up an archiving system
  • SKILL.md covers What This Skill Produces, Required Inputs, Framework: The Strategy Rules and Output Format, plus 7 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Archive Strategy is an agent skill from mohitagw15856/pm-claude-skills. 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.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.

When your agent uses it

  • Asked set up an archiving system
  • Our workspace is drowning in old projects
  • Should things get archived
  • Make history findable without cluttering today

Example prompts

  • “/archive-strategy”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Triggers beat judgment: "archive when the project closes / the year ends / v2 ships / the person leaves" — event-attached rules fire…
  2. Mirror the path, date the layer: _archive/2026/Clients/Acme/ preserves where things lived — provenance is half of future findability, and…
  3. Search-first, index-light: archives are retrieved by search (names per filename-convention make this work), plus one skeleton index per…
  4. Active workspaces show only the living: the payoff metric is the current workspace's size — if this year's project list fits one screen…
  5. The ritual is where it becomes real: project close-out = 20 minutes: final artifacts named per convention → folder moved to the archive…

What it can do on your machine

Read from SKILL.md and the folder at commit 1cbf1f0. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Archive Strategy loads about 1.3k tokens when it runs. Until then it costs about 128 tokens; SKILL.md has 644 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~128
When it runs · the whole SKILL.md, loaded when a task matches
~1.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 644 words, ~1,333 tokens.

Download SKILL.mdSave it as .claude/skills/archive-strategy/SKILL.md (or your agent's skills folder).
name
archive-strategy
description
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.

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:

  • 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 rules ride along into the archive)

Framework: The Strategy Rules

  1. Triggers beat judgment: "archive when the project closes / the year ends / v2 ships / the person leaves" — event-attached rules fire; "archive old stuff sometime" never does. Every trigger names its event and its mover.
  2. Mirror the path, date the layer: _archive/2026/Clients/Acme/ preserves where things lived — provenance is half of future findability, and flat archive dumps ("old-files/") destroy it. The move is a cut-paste of whole folders, never a reorganization-during-archiving (that's how archiving stalls).
  3. Search-first, index-light: archives are retrieved by search (names per filename-convention make this work), plus one skeleton index per year — ten lines: what major things this year's archive holds. Elaborate archive taxonomies serve nobody; the index serves the search-resistant cases.
  4. Active workspaces show only the living: the payoff metric is the current workspace's size — if this year's project list fits one screen, the strategy is working. Archive isn't storage policy; it's attention policy for the space where work happens.
  5. The ritual is where it becomes real: project close-out = 20 minutes: final artifacts named per convention → folder moved to the archive mirror → the year-index line written → links in living docs updated. Attached to the existing close process (the retro, the invoice, the handoff), owned by the project's closer — rituals attached to nothing fire like triggers attached to nothing.
Show full SKILL.md (200 more words)Show less

Output Format

Archive Strategy: [workspace]

The Triggers

EventWhat movesWho moves it

The Destination

[_archive/[year]/[mirrored-path] · whole-folder moves · retention/destruction notes riding along]

Findability

[Search-first note · the year-index skeleton (ten lines) · where the index lives]

The Close-Out Ritual (20 min, attached to [the existing close event])

[Name-final → move → index-line → fix-links — with the owner role named]

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
  • The current workspace visibly shrank — the strategy's actual success metric

Anti-Patterns

  • 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

Example Trigger Phrases

  • "Set up an archiving system."
  • "Our workspace is drowning in old projects."
  • "Make history findable without cluttering today."

© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/archive-strategy of mohitagw15856/pm-claude-skills.

Open the folder on GitHubat commit 1cbf1f0

Compare with similar skills

Archive Strategy next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Archive Strategy compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Archive Strategy this skillmohitagw15856/pm-claude-skills1.4k—~1.3kAutomated safety check: PassMIT
Google Workspace Opsaffaan-m/ECC276k—~299Automated safety check: PassMIT
Lean Formalizewanshuiyin/Auto-claude-code-research-in-sleep17k—~5.4kAutomated safety check: NotesMIT
OpenSpec Bulk Change ArchiverFission-AI/OpenSpec72k2 repos~5.6kAutomated safety check: PassMIT
Workspace Orchestrationdavila7/claude-code-templates33k—~955Automated safety check: PassMIT
Matter Workspaceanthropics/claude-for-legal9.6k3 repos~2.4kAutomated safety check: PassApache-2.0

Similar skills

  • 将 Google 云端硬盘、文档、表格和幻灯片作为一个工作流界面来操作,用于处理计划、追踪器、演示文稿和共享文档。当用户需要查找、总结、编辑、迁移或清理 Google Workspace 资产,而无需使用原始工具调用时使用。

    276k GitHub stars~299 tokensUpdated yesterday
    Documents & OfficeAuto-check passed
  • Lean Formalize

    wanshuiyin/Auto-claude-code-research-in-sleep

    Develop and verify a mathematical proof in Lean, continue an incomplete Lean project, or audit whether it proves the original statement.

    17k GitHub stars~5.4k tokensUpdated 4 days ago
    Auto-check: notes
  • Archives several completed OpenSpec changes in one operation, checking the codebase to resolve spec conflicts rather than archiving blindly.

    72k GitHub starsUsed in 2 repos~5.6k tokens
    DevelopmentAuto-check passed
  • Workspace Orchestration

    davila7/claude-code-templates

    A skill your agent uses when working in a persistent-slot workspace that uses docko.

    33k GitHub stars~955 tokensUpdated yesterday
    Auto-check passed
  • Matter Workspace

    anthropics/claude-for-legal

    Official

    Manage matter workspaces — create, list, switch, close, or detach the active matter so multi-client practitioners keep one client's context separate from every other.

    9.6k GitHub starsUsed in 3 repos~2.4k tokens
    Agent WorkflowsAuto-check passed
  • Apply Gmail labels to matching messages and archive them to keep your inbox clean.

    31k GitHub stars~240 tokensUpdated 4 days ago
    Productivity & AutomationAuto-check passed

More from mohitagw15856/pm-claude-skills

All 1,348 skills in this repo
  • Car Tco

    mohitagw15856/pm-claude-skills

    Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…

    1.4k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed
  • Cs Health Scorecard

    mohitagw15856/pm-claude-skills

    Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.

    1.4k GitHub stars~2.4k tokensUpdated yesterday
    Auto-check passed
  • Exit Waterfall

    mohitagw15856/pm-claude-skills

    Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.

    1.4k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed
  • Feature Prioritisation

    mohitagw15856/pm-claude-skills

    Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.

    1.4k GitHub stars~2k tokensUpdated yesterday
    Auto-check passed
  • Fire Number

    mohitagw15856/pm-claude-skills

    Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.

    1.4k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed
  • Freelance Rate

    mohitagw15856/pm-claude-skills

    Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.

    1.4k GitHub stars~1.2k tokensUpdated yesterday
    Auto-check passed

Questions about Archive Strategy

What does Archive Strategy do?

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…. Archive Strategy is an agent skill from mohitagw15856/pm-claude-skills. 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.

When should I use Archive Strategy?

Archive Strategy fits situations like: asked set up an archiving system; our workspace is drowning in old projects; should things get archived; make history findable without cluttering today.

How do I install Archive Strategy in Claude Code?

Run `npx skills add mohitagw15856/pm-claude-skills --skill archive-strategy -a claude-code`. Or copy the skill folder (skills/archive-strategy in mohitagw15856/pm-claude-skills) into .claude/skills/archive-strategy in your project. Claude Code loads it when a task matches its description.

How do I install Archive Strategy in Codex?

Run `npx skills add mohitagw15856/pm-claude-skills --skill archive-strategy -a codex`. Or copy the skill folder (skills/archive-strategy in mohitagw15856/pm-claude-skills) into .agents/skills/archive-strategy in your project. Codex loads it when a task matches its description.

Can I use Archive Strategy in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mohitagw15856/pm-claude-skills --skill archive-strategy -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/archive-strategy, .gemini/skills/archive-strategy, .github/skills/archive-strategy and .opencode/skills/archive-strategy in your project.

What does Archive Strategy need to run?

SKILL.md names no scripts, command-line tools or credentials: Archive Strategy is instructions for the agent only.

Does Archive Strategy access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Archive Strategy safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Archive Strategy use?

Archive Strategy is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Archive Strategy use?

About 1.3k tokens (SKILL.md is roughly 5.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Archive Strategy?

Skills that share tags, products or a category with Archive Strategy: Google Workspace Ops (affaan-m/ECC, 276k stars), Lean Formalize (wanshuiyin/Auto-claude-code-research-in-sleep, 17k stars), OpenSpec Bulk Change Archiver (Fission-AI/OpenSpec, 72k stars) and Workspace Orchestration (davila7/claude-code-templates, 33k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Archive Strategy?

mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,434 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 9, 2026.

Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.