Archive the current period — collect log entries, generate summary, distil durable facts into the memory base (propose-then-confirm), reset log.md, check upstream. Period follows work.archive_cadence (weekly | bi-weekly | monthly | quarterly | yearly). Supports --force mode. Trigger: "/archive", "archive", "archive week", "archive month", "week archive", "week wrap-up", "archive cadence".
Scanned 9/5/2026
Install to Claude Code
npx -y skills add bks-lab/open-bridge --skill archive --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Archive?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/bks-lab-archive)More formats (shields.io, HTML) on the badges page.
---
name: archive
description: >-
Archive the current period — collect log entries, generate summary, distil
durable facts into the memory base (propose-then-confirm), reset log.md,
check upstream. Period follows work.archive_cadence (weekly | bi-weekly |
monthly | quarterly | yearly). Supports --force mode.
Trigger: "/archive", "archive", "archive week", "archive month",
"week archive", "week wrap-up", "archive cadence".
metadata:
scope: core
---
# Archive
Periodic archive workflow. Read the referenced file ONLY when triggered.
The period is **configurable** — `bridge-config.yaml` `work.archive_cadence`
(`weekly` default, then `bi-weekly` / `monthly` / `quarterly` / `yearly`).
The same key drives `/briefing`'s staleness warning, so the reminder and the
archiver always agree on what "overdue" means.
Archiving **distils before it resets**: `work/archive/` has no reader, so
without a distil step archiving would be forgetting with a backup. Phase 5
proposes durable facts for the memory base — which *is* loaded every session
— and never writes one without confirmation
([`rules/learning-autonomy.md`](../../rules/learning-autonomy.md)).
## Arguments
| Argument | Effect | Default |
|----------|--------|---------|
| `(none)` | Archive the oldest closed period, per `work.archive_cadence` | — |
| `--force` | Archive the current (in-progress) period too | false |
| `--no-distil` | Skip Phase 5; archive without proposing memories | false |
## Prerequisites
`bridge-config.yaml` with `work.enabled: true`. If not: inform and exit.
## Decision Tree
```
User wants to...
├── Archive the period → Read references/workflow.md
├── Change how often it archives → bridge-config.yaml work.archive_cadence
├── Are we behind on anything? → Read skills/briefing/references/upstream-summary.md
└── Questions about archiving → Answer from this file
```
## Activity Types
| Symbol | Name |
|--------|------|
| 🧪 | Testing |
| 💻 | Development |
| 🔬 | Analysis |
| 📋 | Planning |
| 📝 | Documentation |
| 🔧 | DevOps |
| 📅 | Meeting |
| 📧 | Communication |
| 📁 | Documents |
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!