bridge-curatorlisted

Periodic background consolidation pass over the Bridge itself. Three phases: (1) Library pass — scans skills/, protocols/, rules/, docs/ for drift (sleeping skills 30d+, overlapping triggers, description-budget busters, duplicates, umbrella candidates); (2) Queue pass — scans work/_learning/proposals/ for stale pending (30d+), conflict clusters (same target), supersedes relations; (3) User-pattern pass — synthesizes 3-8 bullet observations about user preferences from postmortems + audit-trail + trigger-corrections of the last 30 days, writes append-only to work/_learning/user-patterns.md. All findings land as proposals (source.type=curator-suggestion) in work/_learning/proposals/ — **never direct edits to Bridge files**. Trigger: "/bridge-curator", "bridge curator", "curator", "curation", "weekly review", "library consolidation", "consolidate skills", "what patterns do I have", "user pattern synthesis", "consolidate", "skill consolidation", "umbrella skill".
bks-lab/open-bridge · ★ 8 · AI & Automation · score 74

Install: claude install-skill bks-lab/open-bridge

# Bridge Curator `bridge-curator` is the periodic background-reflection skill. Once a week (configurable), it walks the Bridge's own state and asks three orthogonal questions: 1. **Is the skill library still coherent?** (Library pass) 2. **Is the proposal queue still actionable?** (Queue pass) 3. **What has the system observed about how this user works lately?** (User-pattern pass) The output of all three phases is **always proposals** — markdown files under `work/_learning/proposals/` with `source.type: curator-suggestion`. The curator never edits Bridge files directly. All accepts happen via `/bridge-learn`. This is the deliberate inversion of the autonomy-maximalist curator pattern observed in some agentic frameworks (e.g. Hermes Agent's background-curator-fork). See `rules/learning-autonomy.md` § Layer B for the full design rationale. ## When to run - **Manual:** user says `/bridge-curator`, "bridge curator", "curator", etc. - **Scheduled:** weekly via cron or `/schedule`, if configured in `bridge-config.yaml.learning.curator.schedule`. - **Surface in `/briefing`:** on the configured `auto_surface_in_briefing` day (default Sunday), `/briefing` Stream D adds a "curator due / overdue" one-liner. Running the curator itself stays manual unless user opts into auto-run. ## Arguments | Argument | Effect | Default | |---|---|---| | `(none)` | Run all three passes sequentially | — | | `--pass library` | Only library consolidation | all | | `--pass queue` | Only pro