Skip to main content
NEW · APP STORE Now on iOS · macOS · iPad Android & Windows soon GET IT
Prompts Bunnycdn Automation via Rube MCP

agent tool_use skill risk: medium

Bunnycdn Automation via Rube MCP

Instructs the model to automate Bunnycdn operations through Composio's Bunnycdn toolkit via Rube MCP by first calling RUBE_SEARCH_TOOLS, verifying ACTIVE connection status with RUB…

  • Human review
  • External action: high

SKILL 1 file

SKILL.md
---
name: bunnycdn-automation
description: "Automate Bunnycdn tasks via Rube MCP (Composio). Always search tools first for current schemas."
---
# Bunnycdn Automation via Rube MCP

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

**Toolkit docs**: [composio.dev/toolkits/bunnycdn](https://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.

1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `bunnycdn`
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: "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](https://composio.dev)*

REQUIRED CONTEXT

  • RUBE_SEARCH_TOOLS availability
  • bunnycdn connection status

OPTIONAL CONTEXT

  • specific use_case for Bunnycdn task
  • existing session_id

TOOLS REQUIRED

  • RUBE_SEARCH_TOOLS
  • RUBE_MANAGE_CONNECTIONS
  • RUBE_MULTI_EXECUTE_TOOL
  • RUBE_GET_TOOL_SCHEMAS
  • RUBE_REMOTE_WORKBENCH

ROLES & RULES

  1. Always search tools first for current schemas
  2. Always call RUBE_SEARCH_TOOLS first to get current tool schemas
  3. Always discover available tools before executing workflows
  4. Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
  5. If connection is not ACTIVE, follow the returned auth link to complete setup
  6. Confirm connection status shows ACTIVE before running any workflows
  7. Never hardcode tool slugs or arguments without calling RUBE_SEARCH_TOOLS
  8. Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools
  9. Use exact field names and types from the search results
  10. Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
  11. Reuse session IDs within a workflow
  12. Generate new session IDs for new workflows
  13. Check responses for pagination tokens and continue fetching until complete

EXPECTED OUTPUT

Format
markdown
Constraints
  • always call RUBE_SEARCH_TOOLS first
  • verify ACTIVE connection before execution
  • use exact schemas from search results

SUCCESS CRITERIA

  • Always search first
  • Check connection status is ACTIVE
  • Use schema-compliant arguments from search results
  • Follow core workflow pattern in order

FAILURE MODES

  • Hardcoding tool slugs or arguments
  • Skipping RUBE_SEARCH_TOOLS
  • Executing tools without ACTIVE connection
  • Omitting memory parameter
  • Not reusing session IDs

CAVEATS

Dependencies
  • Rube MCP must be connected
  • Active Bunnycdn connection via RUBE_MANAGE_CONNECTIONS
  • RUBE_SEARCH_TOOLS available
Missing context
  • Concrete example of a full end-to-end workflow with real tool slugs and arguments
  • Target Bunnycdn operations or use-cases the prompt is intended to support
Ambiguities
  • Placeholder text such as "your specific Bunnycdn task" left in example calls
  • Exact JSON structure and field types for RUBE_MULTI_EXECUTE_TOOL arguments not shown

QUALITY

OVERALL
0.73
CLARITY
0.78
SPECIFICITY
0.65
REUSABILITY
0.72
COMPLETENESS
0.80

IMPROVEMENT SUGGESTIONS

  • Replace the placeholder use_case value with one or two realistic examples (e.g., "list pull zones", "purge cache")
  • Add a minimal but complete worked example of Step 3 showing schema-compliant arguments

USAGE

Copy the prompt above and paste it into your AI of choice — Claude, ChatGPT, Gemini, or anywhere else you're working. Replace any placeholder sections with your own context, then ask for the output.

MORE FOR AGENT