dripcel-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/dripcel-automation --openclawDripcel 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_CONNECTIONSwith toolkitdripcel - Always call
RUBE_SEARCH_TOOLSfirst 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_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkitdripcel - 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_CONNECTIONSshows ACTIVE status before executing tools - Schema compliance: Use exact field names and types from the search results
- Memory parameter: Always include
memoryinRUBE_MULTI_EXECUTE_TOOLcalls, 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
Source
git clone https://github.com/ComposioHQ/awesome-claude-skills/blob/master/composio-skills/dripcel-automation/SKILL.mdView on GitHub Overview
Dripcel automation uses Composio's Dripcel toolkit through Rube MCP to run and orchestrate Dripcel operations. It emphasizes discovering current tool schemas before execution to avoid hardcoding slugs or arguments. This ensures your workflows stay up-to-date with tool changes.
How This Skill Works
The skill connects to Rube MCP, validates an active Dripcel connection, and then uses RUBE_SEARCH_TOOLS to fetch current tool schemas. Workflows proceed by selecting a tool slug from the discovery results, validating the session with RUBE_MANAGE_CONNECTIONS, and executing the tool via RUBE_MULTI_EXECUTE_TOOL with the required arguments and memory. This cycle—discover, connect, execute—repeats for robust automation.
When to Use It
- Automating repetitive Dripcel tasks (e.g., bulk operations) to save manual effort
- When tool schemas may change; always fetch current tool slugs and schemas with RUBE_SEARCH_TOOLS
- Before executing any workflow to ensure an ACTIVE dripcel connection via RUBE_MANAGE_CONNECTIONS
- When building multi-step workflows that reuse a session_id across tools
- When performing bulk or paginated operations and needing reliable tool discovery and execution
Quick Start
- Step 1: Add the Rube MCP endpoint (https://rube.app/mcp) as an MCP server in your client and ensure RUBE_SEARCH_TOOLS is available
- Step 2: Establish the Dripcel connection with RUBE_MANAGE_CONNECTIONS and verify ACTIVE status
- Step 3: Discover tools with RUBE_SEARCH_TOOLS, then execute a chosen tool via RUBE_MULTI_EXECUTE_TOOL using the discovered slug and a session_id
Best Practices
- Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas before any execution
- Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status prior to running tools
- Use exact field names and types provided by the discovered tool schemas
- Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
- Reuse session IDs within a workflow and manage pagination tokens when fetching tools
Example Use Cases
- Discover a Dripcel task with RUBE_SEARCH_TOOLS, select the resulting tool_slug, then execute it via RUBE_MULTI_EXECUTE_TOOL in an active session
- Set up the Dripcel connection with RUBE_MANAGE_CONNECTIONS, then run a sequence of tools within a single session_id to complete a workflow
- Periodically refresh tool slugs and schemas with RUBE_SEARCH_TOOLS to avoid hardcoding, then adapt automation accordingly
- Perform bulk Dripcel operations by executing multiple tools in one workflow while maintaining memory across steps
- Use RUBE_REMOTE_WORKBENCH with run_composio_tool() for bulk or bulk-like operations across several Dripcel tools
