Connectors

Connector-backed skills use hosted accounts in skills.md. You connect the service once, then run the skill from the CLI, MCP, API, or dashboard. You do not install connector packages or run a local connector server.

Check Readiness

CLI

skills connectors status gmail

The JSON form is stable for automation:

JSON

skills connectors status gmail --json

Agents can call the MCP tool get_connector_readiness with { "skill": "gmail" }.

Connect An Account

OAuth

skills connectors connect gmail --skill gmail

The command returns a hosted authorization URL. Open it, approve the requested scopes, and return to skills.md. After that, rerun readiness:

Verify

skills connectors status gmail

Run A Connector-Backed Skill

Run

skills run gmail

Run submission fails closed if the account is missing, expired, missing scopes, or platform-connectors is unavailable. The response includes connectorRequirements and connectorPreflight so agents can show the exact next action.

Dashboard

The Skills page shows connector-backed skills with a connector badge. Use Check to refresh readiness. If OAuth is needed, the row exposes a Connect action for the hosted setup URL.

Approvals

Some connector operations require approval. When that happens, the skill run moves to pending_approval, and run status includes connector approval ids, approval URLs, reasons, and current statuses.