Why must I search tools first?

Tool schemas and available inputs change; RUBE_SEARCH_TOOLS returns current slugs, schemas, and execution plans.

What must be true before executing a tool?

RUBE_MANAGE_CONNECTIONS must show ACTIVE for the Onepage toolkit and you should have a valid session_id.

onepage-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Onepage Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/onepage

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Onepage operations using Composio's Onepage toolkit through Rube MCP. This skill emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS and ensuring an ACTIVE Onepage connection via RUBE_MANAGE_CONNECTIONS before running workflows.

How This Skill Works

Start by discovering tools with RUBE_SEARCH_TOOLS to obtain tool slugs, input schemas, and recommended execution plans. Then verify your Onepage connection is ACTIVE with RUBE_MANAGE_CONNECTIONS and execute tools using RUBE_MULTI_EXECUTE_TOOL, passing the exact schema fields and a memory payload; reuse a session_id for related steps and avoid hardcoding slugs.

When to Use It

Automating recurring Onepage operations by orchestrating discovered tools
When tool schemas change, run RUBE_SEARCH_TOOLS first to fetch current slugs and inputs
Before any run, confirm the Onepage connection is ACTIVE via RUBE_MANAGE_CONNECTIONS
Perform bulk Onepage tasks or remote batches using RUBE_MULTI_EXECUTE_TOOL or run_composio_tool
Build reusable workflows by reusing session IDs and iterating over multiple tools

Quick Start

Step 1: Ensure Rube MCP is connected and RUBE_SEARCH_TOOLS responds
Step 2: Discover available Onepage tools with RUBE_SEARCH_TOOLS and pick a tool_slug
Step 3: Execute the selected tool with RUBE_MULTI_EXECUTE_TOOL using memory: {} and the current session_id

Best Practices

Always call RUBE_SEARCH_TOOLS before executing any workflow to get current tool schemas
Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE for the Onepage toolkit
Use exact field names and types from the search results and include memory in calls
Reuse session IDs within a workflow and generate new IDs only for new runs
Handle pagination tokens in API responses and fetch all results until complete

Example Use Cases

Automate a page publish flow by discovering the publish tool and running it with the correct arguments
Bulk update page metadata across multiple pages using RUBE_MULTI_EXECUTE_TOOL
Sync Onepage content to an external CMS by executing a cross-system tool with discovered schema
Automate cleanup tasks that require repeated tool executions with a single session
Migrate a dataset to Onepage by discovering tools, then executing them in sequence

Frequently Asked Questions

Add this skill to your agents