What do I need before starting?

A connected Rube MCP and an active Cloudpress connection, plus using RUBE_SEARCH_TOOLS first to fetch current tool schemas.

How do I discover available Cloudpress tools?

Use RUBE_SEARCH_TOOLS with the Cloudpress use case to fetch tool slugs and input schemas.

Why include memory in Execute calls?

Memory maintains state for the workflow; include an empty object {} if there is no memory to pass.

cloudpress-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Cloudpress Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/cloudpress

Prerequisites

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

Step 2: Check Connection

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

Overview

Automates Cloudpress operations through Composio's Cloudpress toolkit via Rube MCP. It emphasizes discovering current tool schemas before execution and managing connections to ensure reliable automation across Cloudpress workflows.

How This Skill Works

At runtime, you first call RUBE_SEARCH_TOOLS to fetch available tool slugs and input schemas. Next, verify an ACTIVE Cloudpress connection via RUBE_MANAGE_CONNECTIONS. Finally, run the tool with RUBE_MULTI_EXECUTE_TOOL using the discovered tool_slug, the schema-compliant arguments, memory, and a session_id.

When to Use It

Automate a Cloudpress task end-to-end, from discovery to execution
When tool schemas change and you need current slugs and inputs
When validating the Cloudpress connection is ACTIVE before running tools
When performing bulk or remote Cloudpress operations across multiple tasks
When reusing a session across related Cloudpress tasks or workflows

Quick Start

Step 1: RUBE_SEARCH_TOOLS with use_case for Cloudpress to fetch tool slugs and schemas
Step 2: RUBE_MANAGE_CONNECTIONS with toolkit cloudpress and verify ACTIVE status
Step 3: RUBE_MULTI_EXECUTE_TOOL with the discovered tool_slug, schema-compliant arguments, memory, and session_id

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas
Check that RUBE_MANAGE_CONNECTIONS reports ACTIVE before executing tools
Use exact field names and types from the search results
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({})
Reuse session IDs within a workflow and generate new ones only for new workflows

Example Use Cases

Automate a Cloudpress content publish pipeline by discovering tools, connecting, and executing the publish tool with required arguments
Run a bulk Cloudpress update across multiple content items by iterating discovered tool slugs in a single session
Validate a new Cloudpress integration by first fetching current schemas and then invoking the tool with schema-aligned inputs
Handle token expiry by re-authenticating via the auth link and retrying the tool execution
Resume a failed Cloudpress workflow by reusing the existing session_id and re-running the necessary tools

Frequently Asked Questions

Add this skill to your agents