home / skills / composiohq / awesome-claude-skills / page-x-automation

page-x-automation skill

safe

/page-x-automation

This skill automates Page X tasks via Rube MCP, always discovering current tool schemas before execution for reliable, up-to-date automations.

npx playbooks add skill composiohq/awesome-claude-skills --skill page-x-automation

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

Files (1)

SKILL.md

2.8 KB

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

# Page 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](https://composio.dev/toolkits/page_x)

## Prerequisites

- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Page X connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `page_x`
- 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 `page_x`
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: "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_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 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](https://composio.dev)*

Overview

This skill automates Page X tasks through Composio’s Page X toolkit using Rube MCP. It orchestrates discovery of current tool schemas, verifies connections, and executes toolkit actions reliably. The workflow enforces schema compliance and session reuse to avoid runtime errors.

How this skill works

Start by calling RUBE_SEARCH_TOOLS to learn available tool slugs, input schemas, and execution hints. Confirm an active Page X connection with RUBE_MANAGE_CONNECTIONS. Run actions via RUBE_MULTI_EXECUTE_TOOL (or RUBE_REMOTE_WORKBENCH for bulk operations) using schema-compliant arguments and an included memory object.

When to use it

Automating repetitive Page X operations that require up-to-date toolkit schemas.
Running multi-step Page X workflows that need session state or pagination handling.
Executing batch or bulk Page X changes with RUBE_REMOTE_WORKBENCH orchestration.
Integrating Page X actions into larger Claude-driven automation flows.
When tool schemas may change frequently and must be fetched at runtime.

Best practices

Always call RUBE_SEARCH_TOOLS first; never hardcode tool slugs or fields.
Verify connection status with RUBE_MANAGE_CONNECTIONS and require ACTIVE before executing.
Include the memory parameter (use {} if empty) in RUBE_MULTI_EXECUTE_TOOL calls.
Reuse a session_id across a workflow; generate new session_ids for new workflows.
Respect exact field names and types returned by tool discovery to avoid schema errors.
Check for pagination tokens and continue fetching until results complete.

Example use cases

Discover the current Page X publishing tool, then publish a batch of posts with schema-validated arguments.
Validate and refresh an expired Page X connection by following the auth link returned from RUBE_MANAGE_CONNECTIONS.
Run a multi-step workflow that reads Page X items, updates metadata, and confirms changes using RUBE_MULTI_EXECUTE_TOOL.
Perform bulk content migrations on Page X using RUBE_REMOTE_WORKBENCH and run_composio_tool() for parallel execution.
Fetch full tool schemas with RUBE_GET_TOOL_SCHEMAS before building a UI that maps Page X fields.

FAQ

What is the first call I should make in a workflow?

Always call RUBE_SEARCH_TOOLS to retrieve current tool slugs and input schemas.

Do I need API keys to use Rube MCP?

No API keys are required; add https://rube.app/mcp as an MCP server in your client configuration.