composio

# Composio Hub skill for Composio-managed third-party app access from the swarm. The supported surface is the Agent Swarm `x` route: - CLI: `agent-swarm x composio <METHOD> <path> [--body '<json>']` - MCP: `swarm_x` with `target: "composio"` `COMPOSIO_API_KEY` is deployment-scoped and injected by the CLI/API process — you never pass or see it. All paths are **relative** Composio REST paths. > **Per-app playbooks (verified slugs + argument shapes + gotchas):** > [[composio-gmail]] · [[composio-google-calendar]] · [[composio-google-docs]]. > Read the sibling skill for the app you're touching — it lists the verified tool > slugs so you don't have to `/search` blind. ## Core Model - **`user_id`** is the app user whose connected accounts are used. We use the person's **email** as `user_id` (e.g. `t@desplega.ai`). There is **no explicit "create user" call** — a user is created implicitly the first time you reference its `user_id` (e.g. when you create a Connect Link). Don't look for a `POST /users` endpoint; it doesn't exist in this flow. - **Auth config** (`ac_…`) = a project-level OAuth app config (one per toolkit, set up in the Composio dashboard). A project can have several. - **Connected account** (`ca_…`) = a specific user's authorized connection to a toolkit. Persists across sessions under that `user_id`. - **Connect Link** = the short-lived URL the user clicks to authorize OAuth. - **Tool Router session** = a task/conversation runtime context that auto-res...