ops-integratelisted

## Runtime Context ```bash PREFS="${CLAUDE_PLUGIN_DATA_DIR:-$HOME/.claude/plugins/data/ops-ops-marketplace}/preferences.json" PARTNER_REGISTRY=$(jq '.partner_registry // {}' "$PREFS" 2>/dev/null || echo '{}') ``` Parse `$ARGUMENTS`: - Contains `--list` → run **List registered integrations** then exit - Otherwise → run **Onboarding flow** with the service name as first positional argument # OPS ► INTEGRATE ## List registered integrations (`--list`) ```bash jq -r '.partner_registry // {} | to_entries[] | "\(.key): \(.value.base_url) [\(.value.auth_type)]"' "$PREFS" 2>/dev/null ``` Display as a table: ``` Registered integrations: hubspot https://api.hubapi.com [bearer] stripe https://api.stripe.com [bearer] sendgrid https://api.sendgrid.com [api-key] ``` If no integrations registered: `No integrations registered yet. Run /ops:integrate <service-name> to add one.` ## Onboarding flow (5 steps) ### Step 1 — Discover API details If `--url` not provided, use WebSearch to find: - Official API docs URL - Base API URL - Authentication pattern (bearer token / api-key header / basic auth / oauth2) - API key generation URL (where the user gets credentials) - Health/test endpoint (e.g., /healthz, /v1/ping, /me) ### Step 2 — Confirm with user Present findings via AskUserQuestion (≤4 options): ``` Found: <service-name> API — Base URL: <url> — Auth: <auth-type> [Looks correct — continue] [Change base URL] [Change auth type] [Can