What is bunnycdn-automation?

A skill to automate Bunnycdn tasks via Rube MCP using the Bunnycdn toolkit, guided by current tool schemas.

Do I need to always search tools first?

Yes. Tool schemas change, so you must fetch them with RUBE_SEARCH_TOOLS before executing any tool.

Which tools can I run with this skill?

Only the tools returned by RUBE_SEARCH_TOOLS for the Bunnycdn toolkit. Use the provided tool_slug and the exact input schema fields, and include a memory object in each call.

bunnycdn-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Bunnycdn Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/bunnycdn

Prerequisites

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

Step 2: Check Connection

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

Overview

Automates Bunnycdn operations through Composio's Bunnycdn toolkit via Rube MCP. It emphasizes discovering current tool schemas before any action and validating an active Bunnycdn connection. This makes repetitive tasks reliable and up-to-date.

How This Skill Works

The skill uses three core Rube MCP actions: RUBE_SEARCH_TOOLS to fetch current Bunnycdn tool schemas, RUBE_MANAGE_CONNECTIONS to verify or establish an active Bunnycdn connection, and RUBE_MULTI_EXECUTE_TOOL to run the chosen tool with a schema-compliant set of arguments. Always perform a tool discovery before execution and include a memory object and session_id in each run.

When to Use It

You want to automate a routine Bunnycdn task sequence using discovered tools instead of hard-coding tool slugs.
Setting up an end-to-end Bunnycdn workflow for a new project requires verifying the connection and current tool schemas first.
Executing a discovered Bunnycdn tool with the exact input fields from the schema and a session_id in a single workflow.
Running multiple Bunnycdn operations in a single session and reusing the session across steps.
Managing bulk or batch Bunnycdn tasks using RUBE_REMOTE_WORKBENCH for coordinated runs.

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client configuration and verify RUBE_SEARCH_TOOLS responds.
Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkits: ["bunnycdn"] and complete any required auth to ensure ACTIVE status.
Step 3: Use RUBE_SEARCH_TOOLS to discover Bunnycdn tools, then execute a selected tool with RUBE_MULTI_EXECUTE_TOOL using a memory object and a session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS first to get current tool schemas and avoid hard-coded slugs.
Check that the Bunnycdn connection is ACTIVE via RUBE_MANAGE_CONNECTIONS before executing tools.
Use exact field names and types from the search results; do not improvise schema keys.
Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
Reuse session IDs within a workflow and handle pagination tokens when provided by tool responses.

Example Use Cases

Example 1: After asset deployment, purge a list of URLs and refresh the Bunnycdn cache using discovered tools in a single session.
Example 2: Discover Bunnycdn tools, establish a connection, and run purge and cache-refresh operations in sequence.
Example 3: Execute multiple Bunnycdn tasks (purge, add domain, update settings) within one session and reuse the session ID.
Example 4: Continue an automation by reusing a prior session_id to perform follow-up Bunnycdn actions.
Example 5: Perform bulk Bunnycdn ops with RUBE_REMOTE_WORKBENCH and run_composio_tool() for batch processing.

Frequently Asked Questions

Add this skill to your agents