home / skills / composiohq / awesome-claude-skills / onepage-automation

onepage-automation skill

safe

/onepage-automation

This skill automates Onepage tasks via Rube MCP, always discovering current tool schemas before execution to ensure up-to-date workflows.

npx playbooks add skill composiohq/awesome-claude-skills --skill onepage-automation

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

2.9 KB

---
name: onepage-automation
description: "Automate Onepage tasks via Rube MCP (Composio). Always search tools first for current schemas."
requires:
  mcp: [rube]
---

# Onepage Automation via Rube MCP

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

**Toolkit docs**: [composio.dev/toolkits/onepage](https://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.

1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `onepage`
3. If connection is not ACTIVE, follow the returned auth link to complete setup
4. 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](https://composio.dev)*

Overview

This skill automates Onepage tasks through Composio’s Onepage toolkit using the Rube MCP orchestration layer. It provides a repeatable pattern: discover tools, verify connections, and execute toolkit operations safely. The skill emphasizes always searching tools first to retrieve current schemas and recommended execution plans.

How this skill works

The skill calls RUBE_SEARCH_TOOLS to discover available Onepage tools and their exact input schemas, then verifies an active Onepage connection with RUBE_MANAGE_CONNECTIONS. Once tools and connection are confirmed, it runs operations via RUBE_MULTI_EXECUTE_TOOL (or RUBE_REMOTE_WORKBENCH for bulk jobs), always including a memory object and a session ID. It also recommends fetching full schemas via RUBE_GET_TOOL_SCHEMAS when schemaRef is provided.

When to use it

Automating Onepage content creation, updates, or publishing workflows
Integrating Onepage operations into larger agent workflows or pipelines
Performing bulk edits or migrations using RUBE_REMOTE_WORKBENCH
When tool schemas may change frequently and you need the latest field definitions
When you must ensure an active, authenticated Onepage connection before execution

Best practices

Always run RUBE_SEARCH_TOOLS first to retrieve current tool slugs and input schemas
Verify connection status with RUBE_MANAGE_CONNECTIONS and follow any returned auth links until status is ACTIVE
Use exact field names and types from the search result; never hardcode arguments based on assumptions
Include a memory object (even an empty {}) in RUBE_MULTI_EXECUTE_TOOL calls
Reuse session IDs within a single workflow; generate new session IDs for distinct workflows
Watch for pagination tokens in responses and continue fetching until results are complete

Example use cases

Create or update Onepage pages by discovering the current page-create or page-update tool and passing schema-compliant arguments
Bulk migrate content by orchestrating multiple tool calls through RUBE_REMOTE_WORKBENCH and run_composio_tool()
Automate publishing workflows that check connection status, validate fields, and execute publish operations
Embed Onepage operations inside larger agent processes, using search results to adapt to schema changes dynamically
Fetch full tool schemas with RUBE_GET_TOOL_SCHEMAS when you need detailed type or nested-field information

FAQ

Do I need API keys to use Rube MCP?

No API keys are required. Add the MCP endpoint (https://rube.app/mcp) to your client configuration and the MCP server will be available.

What if a tool schema changes during a workflow?

Always call RUBE_SEARCH_TOOLS before each run or step that depends on tool inputs. Re-fetch schemas or use RUBE_GET_TOOL_SCHEMAS when schemaRef is present to avoid mismatched fields.