$ ~/registry/skill/composiohq-composio-skills-cloudflare-automation

SKILL

cloudflare-automation

Name: cloudflare-automation
Author: Composio

Automate Cloudflare configuration, domain, and security tasks through Rube MCP.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

Prompt only, no code
Open source
Community-trusted· 64.7k

Summary

This skill itself is an open-source prompt-style wrapper, but it is designed to connect users to remote Rube MCP and Cloudflare tooling for cloud operations. It does not request local API keys in the material and has strong community trust; the main concern is that actions and related data may be routed through third-party remote services, so the service trust and authorization scope should be verified.

CredentialsCaution

The material states 'No API keys needed', but it requires establishing a `cloudflare` connection via `RUBE_MANAGE_CONNECTIONS` and completing an external auth link, which implies Cloudflare credentials are managed or proxied by a remote service. No local plaintext secret is requested, but there is still the normal risk of mis-scoped or over-broad third-party authorization.

Network egressCaution

The README explicitly requires adding the remote MCP endpoint `https://rube.app/mcp` and using Composio/Rube to discover and execute Cloudflare tools; therefore task descriptions, arguments, session data, and potentially Cloudflare operation data will be sent to the stated third-party service. The endpoint is declared and relevant to the function, so this is expected network egress, but data does not remain local.

Code executionLow risk

System checks indicate this is a `prompt-only` skill, and the material does not instruct installing binaries, spawning local processes, or executing local scripts. Its role is mainly to guide calls to remote MCP tools rather than directly obtaining local code execution capability.

Data accessCaution

The skill is intended to 'Automate Cloudflare operations', which means remote tools may access and modify resources and configurations within the connected Cloudflare account; the README also references session, memory, and pagination parameters, indicating operation context is handled remotely. There is no sign of local filesystem access or unrelated data access, but the scope depends on the granted Cloudflare permissions.

Supply chainLow risk

The source is a GitHub open-source repository, the system marks it as open-source, and community adoption is high (64.7k stars), all of which are strong positive signals. Although the license is unspecified and maintenance status is unknown, and the actual Composio/Rube service implementation cannot be fully audited from this skill material, there are no obvious red flags in the skill's own supply chain.

Recommendations

Before connecting, verify `rube.app`/Composio privacy, logging retention, and data handling practices, and confirm it is the third-party service you intend to use.
Grant Cloudflare the minimum necessary scope; prefer restricted tokens/connections rather than broad account-wide administrative access.
Before using in production, test with a non-production account to validate the actual tool scope returned by `RUBE_SEARCH_TOOLS` and the concrete effects of `RUBE_MULTI_EXECUTE_TOOL`.
Do not include sensitive information unrelated to the Cloudflare task in prompts, because prompts, arguments, and session context may be sent to the remote MCP service.

Audited by: gpt-5.4 · 2026-06-17

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "cloudflare-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/cloudflare-automation/SKILL.md
2. Save it as ~/.claude/skills/cloudflare-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

Cloudflare Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/cloudflare

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["cloudflare"]
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-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `cloudflare`
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

Automate Fluxguard tasks via Rube MCP using current tool schemas first.

ComposioGet→

$ loading_