AgentStack
SKILL verified MIT Self-run

Config Composio

skill-vibesurf-ai-claude-surf-config-composio · by vibesurf-ai

Use when user asks to configure Composio API key, enable or disable Composio toolkits (Gmail, GitHub, Slack, etc.), manage app integrations, or authenticate with external services.

No reviews yet
0 installs
9 views
0.0% view→install

Install

$ agentstack add skill-vibesurf-ai-claude-surf-config-composio

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Config Composio? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Config Composio - Composio Integration Management

Overview

Manage Composio API key and toolkit configurations. Enable/disable app integrations like Gmail, GitHub, Slack, and more.

When to Use

  • User needs to set up Composio API key
  • User wants to enable a toolkit (Gmail, GitHub, Slack, etc.)
  • User needs to disable a toolkit
  • User wants to check which toolkits are available
  • User needs to manage toolkit authentication (OAuth)
  • User wants to configure toolkit tools selection

API Endpoints

Base path: $VIBESURF_ENDPOINT/api/composio

API Key Management

| Action | Method | Endpoint | Description | |--------|--------|----------|-------------| | Check Status | GET | /api/composio/status | Get Composio connection status | | Verify Key | POST | /api/composio/verify-key | Verify and store API key |

Toolkit Management

| Action | Method | Endpoint | Description | |--------|--------|----------|-------------| | List Toolkits | GET | /api/composio/toolkits | Get all available toolkits | | Toggle Toolkit | POST | /api/composio/toolkit/{slug}/toggle | Enable/disable toolkit | | Get Tools | GET | /api/composio/toolkit/{slug}/tools | Get tools for a toolkit | | Update Tools | POST | /api/composio/toolkit/{slug}/tools | Update selected tools | | Connection Status | GET | /api/composio/toolkit/{slug}/connection-status | Check OAuth connection |

Request Examples

Verify API Key

POST /api/composio/verify-key
{
  "api_key": "your-composio-api-key"
}

Enable Toolkit

POST /api/composio/toolkit/gmail/toggle
{
  "enabled": true,
  "force_reauth": false
}

Disable Toolkit

POST /api/composio/toolkit/gmail/toggle
{
  "enabled": false
}

Update Tool Selection

POST /api/composio/toolkit/gmail/tools
{
  "selected_tools": {
    "GMAIL_SEND_EMAIL": true,
    "GMAIL_FETCH_EMAILS": false
  }
}

Common Toolkits

| Toolkit | Description | |---------|-------------| | gmail | Send and receive emails | | github | Repository management, PRs, issues | | slack | Send messages, manage channels | | google_calendar | Event management | | google_sheets | Spreadsheet operations | | notion | Page and database management | | trello | Card and board management | | asana | Task management | | jira | Issue tracking |

OAuth Flow

When enabling a toolkit that requires OAuth:

  1. Enable toolkitPOST /api/composio/toolkit/{slug}/toggle with enabled: true
  2. Check response → If requires_oauth: true, an oauth_url is provided
  3. User authenticates → Open oauth_url in browser to complete OAuth
  4. Verify connectionGET /api/composio/toolkit/{slug}/connection-status

Using Composio Tools

Once toolkits are enabled, their tools become available through the integrations skill:

1. List available tools → GET /api/tool/search?keyword=composio
2. Execute tool → POST /api/tool/execute
   {
     "action_name": "execute_extra_tool",
     "parameters": {
       "tool_name": "cpo.{toolkit}.{action}",
       "tool_arguments": {...}
     }
   }

Tool Naming Convention

Composio tools follow the pattern: cpo.{toolkit_slug}.{action_name}

Examples:

  • cpo.gmail.GMAIL_SEND_EMAIL
  • cpo.github.GITHUB_CREATE_PULL_REQUEST
  • cpo.slack.SLACK_SEND_MESSAGE

Workflow

  1. Check API key statusGET /api/composio/status
  2. Set up API key (if needed) → POST /api/composio/verify-key
  3. List available toolkitsGET /api/composio/toolkits
  4. Enable desired toolkitPOST /api/composio/toolkit/{slug}/toggle
  5. Complete OAuth (if required) → Use provided oauth_url
  6. Use tools → Execute via integrations skill

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.