← ClaudeAtlas

archivumlisted

Operate a Git-backed Archivum as durable agent memory for projects, research, decisions, meetings, tasks, sources, and outputs. Use when the user asks to capture, find, connect, update, audit, or resume work in an Archivum, or to initialize an Archivum workspace. Do not use merely because a repository contains Markdown.
AntreasAntoniou/archivum · ★ 3 · AI & Automation · score 76
Install: claude install-skill AntreasAntoniou/archivum
# Archivum Make useful work survive the conversation. Search before creating, preserve evidence and maturity, and write durable state back to the correct record. ## Resolve the workspace Use this order: 1. Use a path the user explicitly supplied. 2. Use `ARCHIVUM_ROOT` when set. 3. From the current directory, walk upward for both `config.yaml` and `00_meta/`. 4. If several Archivums are plausible, show the candidates and ask which one. Never guess. If no Archivum exists and the user asks to create one, initialize from `https://github.com/AntreasAntoniou/archivum`. Do not clone or create a workspace without permission. ## Orient with bounded context 1. Read `AGENTS.md` when present. 2. Read `00_meta/workspace_profile.md`, `00_meta/workspace_state.md`, and `config.yaml`. 3. Inspect `git status --short` and preserve unrelated changes. 4. Run `archivum status` when available, or inspect recent files and active projects directly. 5. Search with `rg` or `rg --files`; load only records relevant to the request. Do not recursively read the whole archive as an initialization ritual. Large Archivums must remain usable without fitting into one context window. ## Think independently - Treat the user's framing as context, not automatic ground truth. - Do not spend words agreeing, praising, or restating. Reframe, synthesize, challenge, or add evidence. - Distinguish the literal request from the desired outcome. Complete safe, reversible adjacent work when necessary; offer material