What is the purpose of RUBE MCP in this skill?

RUBE MCP provides a centralized way to discover, connect, and execute Firmao tools within Composio, ensuring you always use current tool schemas.

Why must I always search tools first?

Tool schemas change frequently; searching avoids hardcoding slugs and argument names, reducing errors when automating Firmao tasks.

What should I include in multi-tool executions?

Always include memory in RUBE_MULTI_EXECUTE_TOOL calls and provide a valid session_id; ensure the tool slug and arguments come from the latest search results.

firmao-automation

Scanned

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

Files (1)

SKILL.md

2.8 KB

Firmao Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/firmao

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Firmao operations through Composio's Firmao toolkit via Rube MCP. This skill emphasizes discovering current tool schemas before running workflows to avoid brittle, hardcoded tool slugs and arguments.

How This Skill Works

The skill connects to an MCP server, verifies an active Firmao connection, and then discovers available tools with RUBE_SEARCH_TOOLS. It then checks the connection status with RUBE_MANAGE_CONNECTIONS and executes the chosen tool via RUBE_MULTI_EXECUTE_TOOL using the discovered tool_slug and schema-compliant arguments, including a memory object and session_id for context.

When to Use It

When starting a Firmao workflow, always search tools first to retrieve current tool slugs and input schemas.
When establishing a Firmao integration, verify RUBE_MANAGE_CONNECTIONS reports ACTIVE before execution.
When running a task, discover the tool, then execute using the tool_slug and arguments derived from the search results.
When reusing workflows across steps or sessions, reuse the same session_id to maintain context and continuity.
When listing tools, handle pagination tokens from RUBE_SEARCH_TOOLS and fetch all available tools.

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client configuration.
Step 2: Verify RUBE_SEARCH_TOOLS responds to confirm tool schemas are available.
Step 3: Discover tools with RUBE_SEARCH_TOOLS, then check ACTIVE connection with RUBE_MANAGE_CONNECTIONS before executing a tool via RUBE_MULTI_EXECUTE_TOOL.

Best Practices

Always call RUBE_SEARCH_TOOLS before executing to get current tool schemas and avoid stale slugs.
Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE status before tool execution.
Use exact field names and types as provided by the tool schemas in your arguments.
Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({}).
Reuse session IDs within a workflow and generate new ones only for new workflows; watch for pagination in tool lists.

Example Use Cases

Discover the create_invoice tool slug from RUBE_SEARCH_TOOLS for Firmao and execute it with the required fields to generate an invoice.
Connect to Firmao via RUBE_MANAGE_CONNECTIONS with the firmao toolkit, then run a sync operation using the discovered tool slug.
Update a customer record by discovering the update_customer tool, then executing it with the correct arguments within an existing session.
Perform a bulk Firmao operation by using RUBE_REMOTE_WORKBENCH and run_composio_tool with multiple tool slugs in one session.
Fetch full tool schemas with RUBE_GET_TOOL_SCHEMAS to adapt an automation when a tool schema changes, ensuring compatibility.

Frequently Asked Questions

Add this skill to your agents