agentleFS
Sign inStart free
Slava-codeSlava-code/slava-stack/.claude/skills/kb-archive/SKILL.md

kb-archive

Skill0 starsChanged 29 days agoMITView on GitHub

Move a fully superseded KB file to archive/ and fix inbound links. Use when the user says: archive X, retire Y, clean up outdated content.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Verify archive criteria per CONVENTIONS §"Growth rules":

    line 11
  2. Very specific:

    No active decision references it: check decisions/*.md for [[<slug>]] matches.

    line 14
  3. Distinctive:

    If any criterion fails, report to user and ask if they want to override.

    line 15
  4. Very specific:

    If the archived file has supersedes: or is cited by a current file, add a note to the archive/ version stating which file replaced it (for …

    line 17

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

/kb-archive <path>

Usage: /kb-archive brainstorming/2026-04-05-example-slug.md.

  1. Acquire runs/.lock.
  2. Verify archive criteria per CONVENTIONS §"Growth rules":
    • Fully superseded: file has supersedes: coming from a newer file OR user confirms it's retired.
    • Uncited for ARCHIVE_UNCITED_MONTHS: git log -S '[[<slug>]]' --since="<ARCHIVE_UNCITED_MONTHS> months ago" returns empty; grep repo for [[<slug>]] returns only the file itself.
    • No active decision references it: check decisions/*.md for [[<slug>]] matches. If any criterion fails, report to user and ask if they want to override. Do not override silently.
  3. Move: git mv <path> archive/<path> (creates archive/<subfolder>/<file> preserving structure).
  4. If the archived file has supersedes: or is cited by a current file, add a note to the archive/ version stating which file replaced it (for historical continuity).
  5. Regenerate INDEXes: python3 scripts/rebuild-indexes.py. The source folder's INDEX.md will lose the entry; archive/INDEX.md (if configured for listing) will gain it. Stage all modified INDEX.md files.
  6. Commit: archive: <slug>. Push.
  7. Release the lock.

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