What is RUBE_SEARCH_TOOLS and why should I call it first?

RUBE_SEARCH_TOOLS queries the MCP for current tool schemas and available tools; always call it first to avoid hard-coded slugs.

How do I ensure the Faceup connection is ACTIVE?

Call RUBE_MANAGE_CONNECTIONS with the faceup toolkit and verify the status equals ACTIVE before executing any tools.

Is memory required in tool execution?

Yes; include a memory field in RUBE_MULTI_EXECUTE_TOOL calls, even if empty, to preserve state across steps.

faceup-automation

Scanned

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

Files (1)

SKILL.md

2.8 KB

Faceup Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/faceup

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Faceup operations using Composio's Faceup toolkit via Rube MCP. This skill guides discovery of current tool schemas, establishes an Active Faceup connection, and executes tools safely in a repeatable workflow.

How This Skill Works

First, use RUBE_SEARCH_TOOLS to fetch current tool schemas for your Faceup tasks. Then verify the Faceup connection with RUBE_MANAGE_CONNECTIONS and ensure the status is ACTIVE before executing tools with RUBE_MULTI_EXECUTE_TOOL, including a memory field. This approach avoids hardcoding tool slugs and adapts to schema changes.

When to Use It

When you need to automate a Faceup operation end-to-end from discovery to execution
When tool schemas change frequently and you must fetch the latest schemas first
When you must confirm the Faceup connection is ACTIVE before workflows
When running multiple tools in sequence or bulk operations via RUBE_MULTI_EXECUTE_TOOL
When reusing a session and handling pagination in tool discovery results

Quick Start

Step 1: Add the MCP endpoint https://rube.app/mcp as an MCP server in your client config.
Step 2: Run RUBE_SEARCH_TOOLS to verify available tool schemas, then call RUBE_MANAGE_CONNECTIONS with the faceup toolkit and ensure ACTIVE.
Step 3: Use RUBE_MULTI_EXECUTE_TOOL with the discovered tool slug and provide memory: {} and session_id from your search results.

Best Practices

Always call RUBE_SEARCH_TOOLS first and avoid hardcoding tool slugs
Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing
Use exactly the field names and types from the tool schemas
Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty
Reuse session_id within a workflow and manage pagination tokens

Example Use Cases

Discover Faceup tools with a use_case and execute a chosen tool
Establish a FACEUP connection via RUBE_MANAGE_CONNECTIONS and run a tool
Execute a sequence of tools in one workflow using RUBE_MULTI_EXECUTE_TOOL
Handle pagination while discovering tools and continue until complete
Validate tool schemas on each run to avoid breaking changes

Frequently Asked Questions

Add this skill to your agents