Do I always need to search tools first?

Yes. RUBE_SEARCH_TOOLS fetches current tool slugs and input schemas, and tool slugs can change over time.

What if the Diffbot connection is not ACTIVE?

Use RUBE_MANAGE_CONNECTIONS with the diffbot toolkit to authenticate and set the connection status to ACTIVE before executing tools.

Do I need Diffbot API keys?

No API keys are required. Add the MCP server and configure the Diffbot toolkit; authentication is handled through the Rube MCP workflow.

diffbot-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Diffbot Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/diffbot

Prerequisites

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

Step 2: Check Connection

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

Overview

This skill automates Diffbot operations through Composio's Rube MCP toolkit. It emphasizes always searching for current tool schemas before workflows and requires a connected Rube MCP and an active Diffbot connection to run tasks.

How This Skill Works

Connect to Diffbot via Rube MCP and fetch live tool schemas using RUBE_SEARCH_TOOLS, then verify connectivity with RUBE_MANAGE_CONNECTIONS. Once a tool slug and its input schema are identified, execute the task with RUBE_MULTI_EXECUTE_TOOL, including an explicit memory payload and a session_id to maintain workflow context.

When to Use It

When you need to run a Diffbot operation after discovering tools with RUBE_SEARCH_TOOLS
When verifying and establishing a Diffbot connection before execution via RUBE_MANAGE_CONNECTIONS
When selecting a tool slug and input from live schemas rather than hardcoding values
When wiring multi-step workflows and reusing the same session_id across steps
When updating workflows due to changing tool schemas or connectivity status

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client config (no API keys needed).
Step 2: Run RUBE_SEARCH_TOOLS to fetch current Diffbot tool slugs and input schemas.
Step 3: Choose a tool_slug from the results and run RUBE_MULTI_EXECUTE_TOOL with proper arguments, including memory and a session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS first to get current tool slugs and input schemas
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools
Use exact field names and types from the live search results
Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty
Reuse session IDs within a workflow and generate new ones for new workflows

Example Use Cases

Automate a Diffbot article extraction by discovering the appropriate tool slug with RUBE_SEARCH_TOOLS and executing it via RUBE_MULTI_EXECUTE_TOOL with proper arguments
Establish a Diffbot connection, then run a sequence of tools in a single session to process multiple URLs
Update an existing workflow after a tool schema changes by re-running RUBE_SEARCH_TOOLS to fetch fresh slugs
Execute multiple Diffbot tasks in a row using the same session_id and memory to pass intermediate results
Bulk-process a list of pages using RUBE_REMOTE_WORKBENCH with run_composio_tool for efficiency

Frequently Asked Questions

Add this skill to your agents