What are the prerequisites?

Rube MCP connected with RUBE_SEARCH_TOOLS available; an active Tavily connection via RUBE_MANAGE_CONNECTIONS for the tavily toolkit; always call RUBE_SEARCH_TOOLS first to fetch current tool schemas.

How do you handle schema changes?

Always search tools first to fetch current schemas, do not hardcode tool slugs or arguments, and ensure memory and exact field names/types align with the discovered results.

tavily-automation

Scanned

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

Files (1)

SKILL.md

2.8 KB

Tavily Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/tavily

Prerequisites

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

Step 2: Check Connection

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

Overview

This skill automates Tavily operations through Composio's Tavily toolkit using Rube MCP. It emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS, ensuring an active Tavily connection, and executing tools with proper memory and session handling.

How This Skill Works

Begin by discovering available Tavily tools with RUBE_SEARCH_TOOLS to obtain up-to-date slugs and input schemas. Then verify an ACTIVE Tavily connection via RUBE_MANAGE_CONNECTIONS with the tavily toolkit. Finally, execute the chosen tool using RUBE_MULTI_EXECUTE_TOOL, passing the discovered slug, exact field arguments, memory, and a session_id for continuity.

When to Use It

Starting a new Tavily task and you need the latest tool schemas before proceeding.
Reusing a session within a Tavily workflow to maintain continuity.
Verifying the Tavily connection is ACTIVE before tool execution to avoid failures.
Performing bulk Tavily operations via bulk tooling or remote bench features.
Debugging or updating workflows when tool schemas or slugs have changed.

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client configuration.
Step 2: Verify RUBE_SEARCH_TOOLS responds and returns Tavily tool slugs and schemas.
Step 3: Manage the Tavily connection with RUBE_MANAGE_CONNECTIONS and then run a tool via RUBE_MULTI_EXECUTE_TOOL using the discovered slug and memory.

Best Practices

Always call RUBE_SEARCH_TOOLS first to obtain current tool schemas.
Check RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
Use exact field names and types from the search results; avoid hardcoding slugs.
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

Discover Tavily tools with RUBE_SEARCH_TOOLS for a specific Tavily operation and pick the appropriate slug and arguments.
Establish or confirm the Tavily connection using RUBE_MANAGE_CONNECTIONS with toolkit tavily and an active status.
Execute a discovered Tavily tool via RUBE_MULTI_EXECUTE_TOOL using memory, session_id, and the tool_slug.
Perform bulk Tavily operations through RUBE_REMOTE_WORKBENCH with run_composio_tool for parallel tasks.
Fetch full tool schemas using RUBE_GET_TOOL_SCHEMAS to reference schemaRef for validation.

Frequently Asked Questions

Add this skill to your agents