How do I ensure the tool schemas are current?

Always call RUBE_SEARCH_TOOLS before execution to fetch the latest schemas.

How can I verify that the Cloudflare connection is ready?

Use RUBE_MANAGE_CONNECTIONS and ensure the status is ACTIVE before running any tools.

Is the memory parameter required when executing tools?

Yes, include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if it is an empty object {}.

cloudflare-browser-rendering-automation

Scanned

npx machina-cli add skill ComposioHQ/awesome-claude-skills/cloudflare-browser-rendering-automation --openclaw

Files (1)

SKILL.md

3.2 KB

Cloudflare Browser Rendering Automation via Rube MCP

Automate Cloudflare Browser Rendering operations through Composio's Cloudflare Browser Rendering toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/cloudflare_browser_rendering

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["cloudflare_browser_rendering"]
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 Cloudflare Browser Rendering-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `cloudflare_browser_rendering`
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/cloudflare-browser-rendering-automation/SKILL.md

View on GitHub

Overview

This skill automates Cloudflare Browser Rendering tasks through Composio's toolkit via the Rube MCP. It emphasizes using RUBE_SEARCH_TOOLS to fetch current tool schemas, ensures an ACTIVE Cloudflare connection via RUBE_MANAGE_CONNECTIONS, and then executes discovered tools to perform rendering operations.

How This Skill Works

Connect to Rube MCP by adding the MCP endpoint and confirming RUBE_SEARCH_TOOLS responds. Discover available Cloudflare Browser Rendering tools, then check the connection status with RUBE_MANAGE_CONNECTIONS and run a selected tool using RUBE_MULTI_EXECUTE_TOOL with the discovered slug and proper arguments, always including memory.

When to Use It

When starting a new Cloudflare Browser Rendering task and you need to fetch the latest tool schemas
Before executing any rendering task to verify tool slugs and input schemas from RUBE_SEARCH_TOOLS
When you must confirm the Cloudflare connection is ACTIVE before running a workflow
When handling multi-step workflows that require state or memory between tool executions
When performing bulk or repetitive rendering tasks using RUBE_REMOTE_WORKBENCH

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client configuration
Step 2: Verify RUBE_SEARCH_TOOLS responds to fetch Cloudflare Browser Rendering tool schemas
Step 3: Manage connection with RUBE_MANAGE_CONNECTIONS for toolkit cloudflare_browser_rendering and run a sample tool via RUBE_MULTI_EXECUTE_TOOL, ensuring ACTIVE and including memory: {}

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas
Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools
Use exact field names and types from the search results; do not hardcode slugs
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({})
Reuse session IDs for related steps or generate new ones for new workflows

Example Use Cases

Discover available rendering tools and run a specific one with the discovered slug and proper arguments
Verify ACTIVE connection via RUBE_MANAGE_CONNECTIONS before starting a rendering job
Reuse a session across multiple rendering steps to streamline the workflow
Implement a memory state between tool executions within a single rendering workflow
Perform bulk rendering tasks using RUBE_REMOTE_WORKBENCH with run_composio_tool

Frequently Asked Questions

Add this skill to your agents