Capabilities

Capabilities are adopted as plugin packages: bundled skills, tools, and wiring a tenant adopts as one unit. The Plugins surface at /ai/plugins is where that happens: add capabilities to your workspace, then enable them for your agents.

Each row carries plugin, description, category, skill count, version, and status. Installed rows show Manage; available rows show Install. Import plugin brings in from outside the catalog.
Search by name; sort, column, status, and category controls plus advanced filters narrow the list. Category tells you the workload: desktop, documents, crm, creative.
A capability counts as live only when verified in-environment: listed in the environment tool list, credentialed, and within session scope. Installed is adopted, not proven. Code existing is not connected.

Capabilities: plugin packages with category, skills, version, and installed or available status

Sequencing is load-bearing: tools first, skills second, wiring verified last. A skill built on broken tools teaches the agent to fail confidently.
Bindings carry all three coordinates (org, package, connection) with a valid catalog destination. A mapping without all three is meaningless.

Treat /ai/plugins as the source of truth for capability surfaces. Registry reference: Plugin registry. Verification flow and register format: Skills, tools and MCP. Worked path: FDE blank to live.