Composio

Use this skill for app discovery, consent, and execution through QM's authenticated backend. Check availability with GET /v1/composio/toolkits; an absent sandbox API key is expected. Never ask regular users to provision a Composio project key.

Show setup in web chat

When the user asks to connect apps, browse integrations, or show setup again in web chat, include the following directive as its own paragraph in your reply, with blank lines around it:

::connect-apps{}

Write the directive directly, without a code fence or quotation. The web UI renders only the searchable app picker in place. To display the separate Add to Slack action, use ::add-to-slack{} as its own paragraph instead. Include both directives in separate paragraphs when the user asks for full setup. The Slack action is available to administrators; other users should ask their administrator to install QM. Do not repeat the welcome or celebration. Rendering the widget does not authorize any service or require an SDK call; the user chooses an app and completes provider consent. Do not claim accounts are connected without verified status. For Slack conversations, use ordinary authorization links instead of this web-only directive.

When a task needs an app that isn't connected

Check connections before work that depends on an app. If the app is in the catalog but not connected, ask for it in your first reply: do any part that doesn't need the app, show the connect option, and stop. Don't finish a long partial answer first.