← ClaudeAtlas

bridge-onboardlisted

New user onboarding and reconfiguration — discovery-driven setup with permission-gated system scan, evidence-based feature suggestions, and a read-only catalogue of what else Bridge can do. Six-phase wizard (Identity / Discovery / Suggestions / Quick-Wins / Catalog / Validate) with re-entry modes for targeted later activation. Works without GitHub. Upstreams stay empty by default and wire later when the OSS upstream or your own upstream is live. Trigger: "/bridge-onboard", "onboard", "setup", "configure bridge", "new user", "ecosystem scan", "set up bridge", "reconfigure", "reconfigure bridge", "setup wizard".
bks-lab/open-bridge · ★ 8 · AI & Automation · score 74
Install: claude install-skill bks-lab/open-bridge
# Bridge Onboard — Setup Wizard Set up a new Bridge user or reconfigure an existing one. Read the referenced file ONLY when triggered. ## Philosophy — Discover, don't Interrogate A new user came here to configure an assistant, not to inventory their life. Asking abstract questions like "do you file taxes for multiple legal entities?" or "do you have a household mandant?" makes the user defensive — they don't know yet what those features do, so they say "skip" to everything and miss the point. Instead, the wizard: 1. Looks at what's already on the system (with permission) 2. Proposes specific features that match the evidence 3. Shows the rest as a read-only catalogue with "when you need it" 4. Surfaces features proactively later (`feature-discovery` standing-order) when patterns suggest they'd help All of this is **consent-first**: before step 1, the user picks `discovery.mode` — **confined** (default) or **broader**. Confined means the Bridge never scans the machine (other repos, installed apps, devices, files, and mail stay untouched) — you still get every feature, just enabled modularly when you want it via the Phase E catalog, `--add <feature>`, or the feature's `enabled:` flag in `bridge-config.yaml`. Only **broader** unlocks the permission-gated scan in step 1. **The entry point is the four-lane front door** in [`rules/session-start.md`](../../rules/session-start.md) § NEW USER front door — it reflects what Phase 0 detected (origin state, git name), notes the g