tavily-automation_skill

This skill automates Tavily tasks via Rube MCP, ensuring tool schemas are fetched first to optimize workflows.
  • Python

35.4k

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill composiohq/awesome-claude-skills --skill tavily-automation

  • SKILL.md2.8 KB

Overview

This skill automates Tavily tasks through Composio's Tavily toolkit using the Rube MCP orchestration layer. It provides a clear workflow for discovering current tool schemas, managing Tavily connections, and executing multi-tool operations reliably. The skill emphasizes always searching tools first and validating connection status before running workflows.

How this skill works

The skill instructs agents to call RUBE_SEARCH_TOOLS first to retrieve available tool slugs, input schemas, and recommended execution plans. It then verifies the Tavily connection via RUBE_MANAGE_CONNECTIONS and runs operations with RUBE_MULTI_EXECUTE_TOOL (including an explicit memory object and session ID). It includes guidance for pagination, schema compliance, and session reuse across a workflow.

When to use it

  • When you need to run Tavily operations programmatically through Composio and Rube MCP.
  • When tool schemas may have changed and you must discover the latest inputs before calling a tool.
  • When coordinating multi-step Tavily workflows that require connection validation and session state.
  • When executing bulk or parallel Tavily jobs via RUBE_REMOTE_WORKBENCH or multi-execute calls.
  • When building agents that must be robust to schema changes and connection states.

Best practices

  • Always call RUBE_SEARCH_TOOLS at the start of each workflow to fetch current tool slugs and schemas.
  • Verify the Tavily connection is ACTIVE with RUBE_MANAGE_CONNECTIONS before executing any tools.
  • Send a memory object (even if empty) in RUBE_MULTI_EXECUTE_TOOL calls to satisfy the MCP contract.
  • Reuse a session_id for related operations; generate a new session for distinct workflows.
  • Respect exact field names and types from search results—do not hardcode arguments or rely on outdated schemas.
  • Handle pagination tokens in search responses and iterate until all results are retrieved.

Example use cases

  • Discover and run a Tavily data transformation tool: search tools, validate connection, then execute with schema-compliant args.
  • Automate bulk Tavily tasks using RUBE_REMOTE_WORKBENCH and run_composio_tool() for parallel processing.
  • Create an agent that orchestrates a multi-step Tavily workflow, reusing a session_id and preserving memory across steps.
  • Fetch full tool schemas with RUBE_GET_TOOL_SCHEMAS when building integration tests or developer tooling.
  • Recover gracefully from connection issues by guiding users through the auth link returned by RUBE_MANAGE_CONNECTIONS.

FAQ

No API keys are required; add https://rube.app/mcp as an MCP server endpoint in your client configuration.

What if a tool schema changes mid-workflow?

Always call RUBE_SEARCH_TOOLS before each new workflow or critical step to get the latest schema; validate inputs against returned schemas.

Can I omit the memory parameter in multi-execute calls?

No. Include a memory object ({} if empty) in RUBE_MULTI_EXECUTE_TOOL calls to comply with MCP expectations.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational
tavily-automation skill by composiohq/awesome-claude-skills | VeilStrat