How do I discover available Boxhero tools?

Run RUBE_SEARCH_TOOLS with a Boxhero-focused use_case (e.g., 'Boxhero operations') to retrieve tool slugs, input schemas, and recommended execution plans.

Do I need an ACTIVE connection before running Boxhero tools?

Yes. Use RUBE_MANAGE_CONNECTIONS to connect the Boxhero toolkit and ensure the status is ACTIVE prior to execution.

What if tool schemas change?

Always call RUBE_SEARCH_TOOLS to refresh the available tools and their schemas; do not hardcode slugs or argument structures.

boxhero-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Boxhero Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/boxhero

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Boxhero operations through Composio's Boxhero toolkit via Rube MCP. This skill emphasizes discovering current tool schemas before execution and ensuring an ACTIVE Boxhero connection. Always start by RUBE_SEARCH_TOOLS to fetch up-to-date slugs and input schemas.

How This Skill Works

Technically, you discover available Boxhero tools with RUBE_SEARCH_TOOLS, then verify your Boxhero connection with RUBE_MANAGE_CONNECTIONS and ensure status ACTIVE. Finally, execute a chosen tool using RUBE_MULTI_EXECUTE_TOOL with the discovered slug and a memory payload, ensuring schema-compliant arguments and reusing session IDs when appropriate.

When to Use It

Automating routine Boxhero operations (e.g., stock updates or task workflows) via Rube MCP.
When tool schemas change and you need the latest tool slugs and required fields.
To verify and maintain an ACTIVE Boxhero connection before executing any tool.
For bulk or chained Boxhero operations using multiple tools (e.g., multi-step workflows).
When building repeatable Boxhero workflows with session reuse for consistency.

Quick Start

Step 1: Add 'https://rube.app/mcp' as an MCP server and confirm RUBE_SEARCH_TOOLS is available.
Step 2: Run RUBE_SEARCH_TOOLS with use_case 'Boxhero operations' to fetch tool slugs and input schemas.
Step 3: Run RUBE_MANAGE_CONNECTIONS with toolkits: ['boxhero'] and verify the session is ACTIVE before executing tools.

Best Practices

Always call RUBE_SEARCH_TOOLS first to obtain current tool schemas and slugs.
Verify the Boxhero connection is ACTIVE via RUBE_MANAGE_CONNECTIONS before execution.
Use exact field names and types from the tool schemas in your arguments.
Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
Reuse session IDs within a workflow or generate new ones for new workflows; watch for pagination in tool lists.

Example Use Cases

Automate a daily Boxhero stock check by discovering tools, authenticating, and running the stock-update tool with a scheduled session.
Create a recurring Boxhero workflow with a named session and reuse the session_id across days.
Fetch the latest Boxhero tool schemas with RUBE_GET_TOOL_SCHEMAS and then execute a specific tool slug with validated inputs.
Perform bulk Boxhero operations using RUBE_REMOTE_WORKBENCH and run multiple tools in sequence.
Ensure the Boxhero connection is ACTIVE before a critical update; re-authenticate if the status changes.

Frequently Asked Questions

Add this skill to your agents