capability-brokerlisted

Turns a capability gap into a gated acquisition. When the user needs a tool or capability the Bridge can't do yet — and no existing skill, CLI, MCP, or account covers it — this skill runs a false-gap guard, then OFFERS (never auto-acts) to either research + provision the right tool, or scaffold a dedicated skill, and captures the outcome as a learning so the gap never recurs unaddressed. It is the forward / acquisition arm of the Bridge learning loop (the retrospective arms are task-close-postmortem, bridge-audit, bridge-curator); it composes with them and with rules/learning-autonomy.md, never reinventing them. Hands skill authoring to skill-creator and bounded research to deep-research. Trigger phrases: "the bridge can't do that", "you can't do X yet", "there's no skill for this", "we don't have a tool for", "set this up so it sticks", "build a skill for this", "is there a tool that", "capability gap", "self-extend", "teach yourself to", "add this capability".
bks-lab/open-bridge · ★ 8 · AI & Automation · score 74

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

# Capability Broker The **acquisition** arm of the Bridge learning loop. The other arms look backward and refine what exists (`task-close-postmortem`, `bridge-audit`, `bridge-curator`); this one looks forward and **gains a new capability** — a tool or a skill — when the user hits something the Bridge can't do yet. It **proposes, it never auto-acts.** Every install, every outward step, every persistent write is propose-then-confirm. Same human-gate-at-every-layer posture as `rules/learning-autonomy.md` — this skill is bound by that rule, not an exception to it. Read this file only when triggered. Full procedures live in `references/` (progressive disclosure) — load the one you need, not all four. ## When this skill runs | Entry | Mode | |---|---| | The `capability-gap-offer` standing-order detects a true gap | **Auto-offer** — surface the 4-way offer, then route | | User says "the bridge can't do X", "build a skill for this", "is there a tool that…" | **Direct** — same flow, user-initiated | | User picks a route from a prior offer (`r`/`s`/`o`/`d`) | **Route** — jump to the chosen branch | ## The flow (one screen) 1. **Guard** — confirm it's a *true* gap, not a false one. → `references/gap-detection.md` 2. **Offer** — one question, four routes. Never silently fail or silently one-off. 3. **Route**: - `[r]` research + provision a tool → `references/research-playbook.md` → decision tree - `[s]` scaffold a skill → decision tree → hand to `skill-creator` - `[o]` on