bench-automation

Automate Bench operations through Composio toolkits using Rube MCP integration.

74.2k|8.5k|Updated Oct 17, 2025
One-click install
npx skills add https://github.com/ComposioHQ/awesome-claude-skills --skill bench-automation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bench-automation
Source: https://github.com/ComposioHQ/awesome-claude-skills/tree/main/composio-skills/bench-automation
Command: npx skills add https://github.com/ComposioHQ/awesome-claude-skills --skill bench-automation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the manual overhead of managing Bench operations by providing a standardized, automated interface for tool discovery and execution.

Core Features & Use Cases

  • Automated Tool Discovery: Dynamically fetch current tool schemas and execution plans via Rube MCP.
  • Connection Management: Verify and maintain active Bench connections to ensure reliable workflow execution.
  • Multi-Tool Execution: Execute complex, multi-step Bench tasks using a unified interface for tool invocation.

Quick Start

Ask the agent to search for available Bench tools and execute the required operation using the Rube MCP gateway.

Frequently Asked Questions about bench-automation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Bench tasks with this skill?

Use the Rube MCP integration to search for available tools, verify your Bench connection status, and execute tasks using the Rube multi-execute tool command.

What should I do if my Bench connection is not active?

Call the RUBE_MANAGE_CONNECTIONS command with the bench toolkit to retrieve the authentication link and complete the setup process.

Why must I call RUBE_SEARCH_TOOLS before executing tasks?

Tool schemas and available arguments change frequently; calling RUBE_SEARCH_TOOLS ensures you use the most current definitions and avoid execution errors.

Can I reuse session IDs for different workflows?

No, you should generate new session IDs for distinct workflows to maintain state isolation and prevent interference between different Bench operations.

What is the purpose of the memory parameter?

The memory parameter is a required field for RUBE_MULTI_EXECUTE_TOOL calls that maintains state context during execution, even if it is passed as an empty object.