orbid-gapslisted

Use when the user asks what is missing on an Orbid product, open gaps, 缺口, 缺什么证, query_gaps, critical/open/waive rows, or remaining compliance holes. Requires connected Orbid MCP. Not for waiving a gap (that stays in Orbid), product match, or Excel fill.
Leon-SG/orbid-skills · ★ 1 · AI & Automation · score 73

Install: claude install-skill Leon-SG/orbid-skills

# Orbid gaps List **open product gaps** for this org. Same rows as Orbid `/gaps`. ## Gate Need Orbid MCP `query_gaps` (and usually `search_product_catalog` / `list_sessions`). Names may be prefixed. Missing / 401 → stop. Connect `https://app.orbid.dev/mcp`. Do not invent gap rows. ## Steps 1. `query_gaps` requires a product **UUID**, never a model name. If the user said “EP70” / a model, `search_product_catalog` first and take the id from the hit. MCP may resolve from session context; **this skill still must pass a UUID** so a host without Orbid session context cannot dump the wrong product. 2. Call `query_gaps` with `productId` (UUID). Optional: `sessionId` from `list_sessions` if they scoped to a bid; `smart` one of `critical` | `open` | `review` | `change` | `waive`. Never pass org_id, workspaceId, or skipAutoFill. 3. Summarize from JSON only. Do not mark waive / yellow / decide — those writes are not on MCP. Send the user to the Orbid bid or gaps UI to decide. ## Do not - Pass a model string as `productId`. - Call `run_match` (use **orbid-match**) unless they also asked to match. - Claim a gap was waived or assigned.