What should I always do before executing tools?

Always call RUBE_SEARCH_TOOLS to fetch current tool slugs and input schemas before running any workflow.

What is required to start?

An active Waboxapp connection via RUBE_MANAGE_CONNECTIONS with the toolkit set to 'waboxapp' and RUBE_SEARCH_TOOLS availability.

waboxapp-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Waboxapp Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/waboxapp

Prerequisites

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

Step 2: Check Connection

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

Overview

This skill automates Waboxapp operations using Composio's Waboxapp toolkit through Rube MCP. It emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS before each workflow and validating an active Waboxapp connection. Prerequisites include a connected Rube MCP and an ACTIVE Waboxapp session.

How This Skill Works

Begin by discovering available tools with RUBE_SEARCH_TOOLS to obtain current tool slugs and input schemas. Next, verify the Waboxapp connection using RUBE_MANAGE_CONNECTIONS and ensure the status is ACTIVE. Finally, execute the chosen tool via RUBE_MULTI_EXECUTE_TOOL, supplying the discovered slug, schema-compliant arguments, and a memory object (even if empty) within an active session.

When to Use It

When you need to automate Waboxapp tasks without custom coding
When tool schemas may change, so you must fetch them first
When integrating Waboxapp actions into longer Composio workflows
When validating and reusing a session across multiple tool runs
When performing bulk or chained operations using discovered tools

Quick Start

Step 1: RUBE_SEARCH_TOOLS with use_case: 'Waboxapp operations' to discover tools
Step 2: RUBE_MANAGE_CONNECTIONS with toolkits: ['waboxapp'] and a valid session_id
Step 3: RUBE_MULTI_EXECUTE_TOOL with tool_slug from search results, proper arguments, memory: {}, and the session_id

Best Practices

Always call RUBE_SEARCH_TOOLS before selecting a tool
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before execution
Use exact field names and types from the search results
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
Reuse session IDs within a workflow and refresh for new workflows

Example Use Cases

Discover tools for Waboxapp, pick a tool_slug, and run with required args
Validate connection status as ACTIVE before running any workflow
Chain multiple Waboxapp tools in a single session using RUBE_MULTI_EXECUTE_TOOL
Fetch tool schemas via RUBE_GET_TOOL_SCHEMAS when schemas update
Handle pagination by continuing RUBE_SEARCH_TOOLS calls until all tools are retrieved

Frequently Asked Questions

Add this skill to your agents