right-composiolisted

# /right-composio — Composio MCP playbook **Read this BEFORE your first `mcp__right__composio__*` call this session, and again on resume.** The defaults (no workbench, fresh search every turn, one tool per call) will bury you in context tokens. Composio is a gateway: one MCP server fronts 250+ external services (Notion, Gmail, Calendar, Slack, GitHub, ...). Tool surface is narrow (~7 meta-tools) but responses can be huge. Two biggest context risks: dumping list/search/fetch payloads into context, and looping single tool calls when one MULTI_EXECUTE would do. ## When to Activate - The user's request maps to a Composio-fronted service. - You're about to invoke `mcp__right__composio__*` and need to decide: workbench yes/no, MULTI_EXECUTE vs single, search_tools first? - If composio is not in `mcp__right__rightmeta__mcp_list`, this skill does not apply — ask the user to open `/mcp` and add Composio in the dashboard. ## Workbench discipline `mcp__right__composio__COMPOSIO_MULTI_EXECUTE_TOOL` has a `sync_response_to_workbench` field. `true` → response stored in Composio's remote workbench, you get a reference. `false` (default) → full payload lands in your context. **`sync_response_to_workbench: true` when:** - Tool slug contains `_LIST_`, `_SEARCH_`, `_FETCH_`, `_GET_ALL`, `_PAGES`, `_THREADS` (collections). - Batching 2+ tools in one MULTI_EXECUTE call. - Expecting prose bodies (email content, Notion page text). - Follow-up MULTI_EXECUTE will act on the result — pass