$ ~/registry/skill/composiohq-composio-skills-adrapid-automation

SKILL

adrapid-automation

Name: adrapid-automation
Author: Composio

Automate Adrapid tasks via Rube MCP after checking current tool schemas.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

Prompt only, no code
Open source
Community-trusted· 64.7k

Summary

This skill appears to be an open-source prompt/documentation artifact with no direct local secret requirement or embedded executable code. However, it is designed to connect to remote Rube MCP/Composio services and operate Adrapid tools, so it carries normal third-party connectivity and data-flow considerations, making it cautionary rather than high risk.

CredentialsCaution

The material says 'no API keys needed,' but it requires establishing an active `adrapid` connection via `RUBE_MANAGE_CONNECTIONS` and completing an auth link flow. That implies real credentials are likely created and managed in the external connection flow; the docs do not specify token scope, storage, or revocation details.

Network egressCaution

It explicitly requires adding the remote MCP endpoint `https://rube.app/mcp` and using Composio/Rube to discover and execute Adrapid tools. User prompts, session IDs, tool arguments, and possibly business data are therefore expected to be sent to that stated third-party service. The endpoint is declared and function-related, with no clear sign of unrelated or hidden exfiltration.

Code executionLow risk

Based on the material, this is a prompt/README-style skill that documents how to call remote MCP tools; it does not include local scripts, install commands, or instructions to directly execute local system processes. The 'Always search tools first' instruction is operational guidance, not a local code-execution red flag.

Data accessCaution

The skill itself does not declare local file or system access, but when executing remote Adrapid operations, the effective access scope depends on the authorized Adrapid account and the discovered tool schemas. The documentation does not define least-privilege boundaries, so it should be assumed to access data relevant to Adrapid workflows.

Supply chainLow risk

The source is an open GitHub repository with very strong community adoption (64.7k stars), both of which are meaningful risk-reducing signals; the material also indicates it is prompt-only. Although the license is unspecified and maintenance status is unknown, those governance gaps alone do not justify a high-risk rating.

Recommendations

Review Rube/Composio and Adrapid privacy, data retention, and credential-handling practices before connecting.
Use a least-privilege Adrapid account for authorization, and regularly review revocable connections and active sessions.
Before sending sensitive business data, inspect the tool schemas and argument meanings returned by `RUBE_SEARCH_TOOLS`.
Validate the workflow in an isolated test environment before using production data.

Audited by: gpt-5.4 · 2026-06-17

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "adrapid-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/adrapid-automation/SKILL.md
2. Save it as ~/.claude/skills/adrapid-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

Adrapid Automation via Rube MCP

Automate Adrapid operations through Composio's Adrapid toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/adrapid

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
Active Adrapid connection via RUBE_MANAGE_CONNECTIONS with toolkit adrapid
Always call RUBE_SEARCH_TOOLS first to get current tool schemas

Setup

Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.

Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
Call RUBE_MANAGE_CONNECTIONS with toolkit adrapid
If connection is not ACTIVE, follow the returned auth link to complete setup
Confirm connection status shows ACTIVE before running any workflows

Tool Discovery

Always discover available tools before executing workflows:

RUBE_SEARCH_TOOLS
queries: [{use_case: "Adrapid operations", known_fields: ""}]
session: {generate_id: true}

This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls.

Core Workflow Pattern

Step 1: Discover Available Tools

RUBE_SEARCH_TOOLS
queries: [{use_case: "your specific Adrapid task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["adrapid"]
session_id: "your_session_id"

Step 3: Execute Tools

RUBE_MULTI_EXECUTE_TOOL
tools: [{
  tool_slug: "TOOL_SLUG_FROM_SEARCH",
  arguments: {/* schema-compliant args from search results */}
}]
memory: {}
session_id: "your_session_id"

Known Pitfalls

Always search first: Tool schemas change. Never hardcode tool slugs or arguments without calling RUBE_SEARCH_TOOLS
Check connection: Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools
Schema compliance: Use exact field names and types from the search results
Memory parameter: Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({})
Session reuse: Reuse session IDs within a workflow. Generate new ones for new workflows
Pagination: Check responses for pagination tokens and continue fetching until complete

Quick Reference

Operation	Approach
Find tools	`RUBE_SEARCH_TOOLS` with Adrapid-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `adrapid`
Execute	`RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs
Bulk ops	`RUBE_REMOTE_WORKBENCH` with `run_composio_tool()`
Full schema	`RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef`

Powered by Composio

Automate AI/ML API workflows via Rube MCP, checking latest tool schemas first.

ComposioGet→

$ loading_