← ClaudeAtlas

arguslisted

Preserve durable context from conversations and completed work by routing commitments, evidence, decisions, preferences, and project state to their canonical Git-backed records. Use when the user asks to archive, remember, checkpoint, capture context, update an Archivum-style workspace, or close the loop; also use at natural milestones when workspace instructions require durable-state capture.
AntreasAntoniou/argus-skill · ★ 0 · Code & Development · score 72
Install: claude install-skill AntreasAntoniou/argus-skill
# Argus Keep a hundred eyes on the live context, but preserve only the delta that should outlive it. Do not archive the conversation itself. ## Run one checkpoint 1. Identify durable changes only: - explicit decisions, corrections, and stable preferences; - promises, deadlines, waiting-on states, and changed priorities; - project state, evidence, results, blockers, and next actions; - reusable methods, sources, and outputs. 2. Exclude unselected brainstorming, conversational filler, duplicated summaries, unsupported claims, and secrets outside their authorised store. 3. Discover the home registry and candidate archives: ```bash python3 scripts/discover_archivums.py --json ``` Resolve `scripts/` relative to this installed skill. Prefer an explicit `--registry`, then `ARCHIVUM_REGISTRY`, then `$ARCHIVUM_HOME/00_meta/archivum_registry.toml`. If no registry resolves the choice and several archives remain plausible, ask rather than guess. 4. Route each delta using [routing.md](references/routing.md). One checkpoint may update several surfaces, but each fact has one canonical owner. 5. For commitment-shaped state, use the workspace's configured commitment system rather than inventing a parallel ledger. Read its contract before mutation. 6. For resource-shaped state or substantial autonomous work, use the configured budget authority rather than creating a second resource ledger. Gate expensive work and record actual usage where that system requi