page-x-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/page-x-automation --openclawPage X Automation via Rube MCP
Automate Page X operations through Composio's Page X toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/page_x
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Page X connection via
RUBE_MANAGE_CONNECTIONSwith toolkitpage_x - Always call
RUBE_SEARCH_TOOLSfirst 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_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkitpage_x - 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: "Page X 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 Page X task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["page_x"]
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_CONNECTIONSshows ACTIVE status before executing tools - Schema compliance: Use exact field names and types from the search results
- Memory parameter: Always include
memoryinRUBE_MULTI_EXECUTE_TOOLcalls, 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 Page X-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit page_x |
| 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/page-x-automation/SKILL.mdView on GitHub Overview
Page X Automation via Rube MCP enables automating Page X operations through Composio's Page X toolkit using the RUBE MCP interface. It emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS, establishing an active Page X connection, and executing tools via RUBE_MULTI_EXECUTE_TOOL. Keeping tool schemas up-to-date is essential to reliable automation.
How This Skill Works
First, discover available Page X tools using RUBE_SEARCH_TOOLS to obtain current tool slugs and input schemas. Next, verify the Page X connection with RUBE_MANAGE_CONNECTIONS and ensure the status is ACTIVE. Finally, execute the chosen tool through RUBE_MULTI_EXECUTE_TOOL, supplying the discovered slug, memory (even if empty), and session_id; always fetch current schemas before each run.
When to Use It
- When starting a Page X automation and you need current tool schemas instead of hardcoded slugs.
- When chaining multiple Page X operations in a single workflow requiring coordinated tool execution.
- When verifying that the Page X connection is ACTIVE before running tools.
- When tool schemas may change and you must rely on up-to-date field names and types.
- When handling paginated Page X results and continuing fetches until completion.
Quick Start
- Step 1: Run RUBE_SEARCH_TOOLS with a Page X use_case to fetch current tool schemas.
- Step 2: Run RUBE_MANAGE_CONNECTIONS with toolkits: ["page_x"] and verify ACTIVE status.
- Step 3: Run RUBE_MULTI_EXECUTE_TOOL with a discovered tool slug, the required arguments, memory: {}, and session_id from the search output.
Best Practices
- Always call RUBE_SEARCH_TOOLS before executing any Page X workflow to fetch current schemas.
- Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE before tool execution.
- Use exact field names and types from the search results; avoid hardcoding slugs or args.
- Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({}).
- Reuse session IDs within a workflow and generate new ones only for separate workflows.
Example Use Cases
- Automate a Page X data extraction and update flow using the discovered tool slugs from RUBE_SEARCH_TOOLS.
- Chain multiple Page X operations in a single run by sequencing RUBE_SEARCH_TOOLS, RUBE_MANAGE_CONNECTIONS, and RUBE_MULTI_EXECUTE_TOOL.
- Validate and route Page X tasks by confirming an ACTIVE connection before each tool execution.
- Handle paginated Page X tool results by iteratively fetching tokens and continuing until complete.
- Perform bulk Page X operations using RUBE_REMOTE_WORKBENCH with run_composio_tool() and discovered schemas.
