bridge-overlaylisted

Subscribe a Bridge to an ORG OVERLAY — a git repo an organisation publishes that ships its shared config (contexts, projects, mandants, accounts, org skills/agents/standing-orders, an ecosystem fragment) as a flat mirror tree. /overlay add <git-url> sparse-clones the overlay, validates its manifest, previews a per-file plan with risk flags, and materializes COPIES into your repo under a lockfile — never block-merging your config, never clobbering your edits (3-way merge), never touching CORE. sync/apply/status/diff/remove/list manage the subscription over time. The overlay is the LOWER layer; your user files always win. Trigger: "/overlay", "org overlay", "subscribe to overlay", "materialize org config", "pull org overlay", "unsubscribe overlay", "add org config by git url", "list overlays", "overlay status", "overlay diff".
bks-lab/open-bridge · ★ 8 · AI & Automation · score 74

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

# Bridge Overlay — subscribe to an org's config bundle An **org overlay** is a git repo an organisation publishes so its members' Bridges can share config without each person hand-copying files. It mirrors a **flat tree** of files (`tree/<path>` → `<path>`), every file `scope: org`, declared by a root `overlay.manifest.yaml`. `/overlay` is the consumer side: it subscribes, materializes COPIES under a lockfile, and keeps them in sync. It is the **mirror-image** of the push skills: | Skill | Direction | Unit | |---|---|---| | `/promote` · `/bridge-sync` | **push** your `scope:org`/`core` commits **up** to an upstream | commits | | `/overlay` | **pull** an org's published config **down** into your repo | manifest-declared files | Read the referenced file ONLY when triggered. ## When to use - An org gives you a git URL: "subscribe your Bridge to our overlay" - You want the org's shared contexts / projects / mandants / accounts / org skills materialized locally and kept current - You already subscribed and want to pull updates (`sync`), preview them (`diff`), re-materialize offline (`apply`), check freshness (`status`), or end the subscription (`remove`) **NOT** for: - Publishing an overlay (that's the org's job — see `references/authoring.md`) - Pushing YOUR changes upstream (`/promote`, `/bridge-sync`) - One-off file copies with no ongoing subscription (just copy the file) ## What an overlay carries An overlay ships an org's `scope: org` building blocks as a flat