What is Daffy Automation via Rube MCP?

It’s a workflow that automates Daffy operations by discovering current tool schemas with RUBE_SEARCH_TOOLS and executing tools through RUBE_MULTI_EXECUTE_TOOL, ensuring up-to-date inputs and an ACTIVE connection.

Do I need API keys to set this up?

No API keys are needed. You just add the MCP endpoint (https://rube.app/mcp) and follow the setup steps to connect and authenticate.

What if tool schemas change frequently?

Always search tools first with RUBE_SEARCH_TOOLS to fetch current slugs and field names, then adjust your arguments accordingly; never hardcode slugs or schema details.

daffy-automation

Scanned

npx machina-cli add skill ComposioHQ/awesome-claude-skills/daffy-automation --openclaw

Files (1)

SKILL.md

2.8 KB

Daffy Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/daffy

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["daffy"]
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 Daffy-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `daffy`
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/daffy-automation/SKILL.mdView on GitHub

Overview

Automate Daffy operations through Composio's Rube MCP toolkit. The workflow emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS before execution to avoid hardcoding inputs.

How This Skill Works

Prerequisites: connect Rube MCP and ensure RUBE_SEARCH_TOOLS is available; manage connections for the daffy toolkit with RUBE_MANAGE_CONNECTIONS. Core pattern: 1) Discover tools using RUBE_SEARCH_TOOLS to obtain tool slugs and schemas, 2) Check connection status to ensure ACTIVE, 3) Execute the chosen tool via RUBE_MULTI_EXECUTE_TOOL with the discovered slug, proper arguments, memory, and a session_id.

When to Use It

When you need to automate routine Daffy operations and want up-to-date tool schemas
When setting up a new Daffy workflow end-to-end and validating connectivity first
When tool schemas change and hardcoded slugs/args would break your automation
When running multiple Daffy tasks in a single session to optimize throughput
When reusing a session ID within a workflow to maintain state across steps

Quick Start

Step 1: Ensure Rube MCP is configured and RUBE_SEARCH_TOOLS responds
Step 2: Use RUBE_SEARCH_TOOLS to find Daffy tool slugs and establish a session_id
Step 3: Execute a discovered tool with RUBE_MULTI_EXECUTE_TOOL using the slug, proper arguments, memory, and the session_id

Best Practices

Always run RUBE_SEARCH_TOOLS before executing any tool to fetch current schemas
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before tool execution
Use exact field names and types from the search results; avoid hardcoding
Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty
Reuse session IDs within a workflow; generate new ones for separate workflows

Example Use Cases

Discover Daffy operations with RUBE_SEARCH_TOOLS, connect via RUBE_MANAGE_CONNECTIONS, then run a single tool with RUBE_MULTI_EXECUTE_TOOL and memory to fetch a report
Automate a sequence of Daffy tasks by discovering multiple tool slugs from search results and executing them in a single session
Update a Daffy workflow when tool schemas are updated by re-running RUBE_SEARCH_TOOLS and adapting arguments
Batch process several Daffy tasks using RUBE_REMOTE_WORKBENCH to orchestrate multiple tool runs
Validate tool schemas with RUBE_GET_TOOL_SCHEMAS to ensure compatibility before deployment

Frequently Asked Questions

Add this skill to your agents