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

SKILL

dripcel-automation

Name: dripcel-automation
Author: Composio

Automate Dripcel tasks via Rube MCP with schema lookup first.

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-only wrapper from a relatively trusted source, with no direct local secret requirement or local code execution. The main security consideration is its dependence on external Rube MCP and a Dripcel account connection, where actual data access and egress would occur through those external service paths.

CredentialsCaution

The material says 'No API keys needed,' but it requires an ACTIVE `dripcel` connection via `RUBE_MANAGE_CONNECTIONS` and completing authorization through a returned auth link; this suggests credentials are likely brokered by Rube/Composio rather than absent. No direct secret collection or exposure by the skill is shown, but there is the usual caution around third-party delegated connections and potential misuse of that connection.

Network egressCaution

The README explicitly requires adding the remote MCP endpoint `https://rube.app/mcp` and performing actions through Composio's Dripcel toolkit; user queries, tool arguments, and related business data are therefore expected to be sent through that external service path. The endpoint and purpose are clearly declared, making this normal for the tool type, but data does leave the current client environment.

Code executionLow risk

System checks indicate this is prompt-only, and the material does not state any need to spawn local processes, run scripts, or invoke a system shell. It mainly instructs how to use existing MCP tools rather than carrying its own local execution logic.

Data accessCaution

There is no indication of local file or system-level data permissions, but the documentation explicitly supports automating Dripcel operations via `RUBE_MULTI_EXECUTE_TOOL` and mentions session reuse and pagination, indicating it can read or modify remote business data within the authorized Dripcel account scope. The effective data scope depends on the permissions granted through the external Dripcel/Composio connection.

Supply chainLow risk

The source is an open-source GitHub repository with high community adoption (64.7k stars), which are strong risk-reducing signals; the current material also shows no obfuscated installation steps, suspicious scripts, or injection-style red flags. Remaining minor unknowns are the missing license declaration and unclear maintenance status, so repository updates and the exact skill contents should still be reviewed.

Recommendations

Connect to `rube.app/mcp` only when necessary, and verify that your organization permits Dripcel-related data to be processed by Rube/Composio.
Before completing the `dripcel` authorization, review the exact OAuth/connection scopes requested and prefer a least-privilege account.
Avoid sending unnecessary sensitive data in tool arguments, and regularly revoke unused Rube/Dripcel connections.
Before deployment, review the actual skill contents in the GitHub repository and check its recent maintenance status.

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 "dripcel-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/dripcel-automation/SKILL.md
2. Save it as ~/.claude/skills/dripcel-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

Dripcel Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/dripcel

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
Active Dripcel connection via RUBE_MANAGE_CONNECTIONS with toolkit dripcel
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 dripcel
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: "Dripcel 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 Dripcel task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["dripcel"]
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 Dripcel-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `dripcel`
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 Autom workflows via Rube MCP while checking current tool schemas first.

ComposioGet→

$ loading_