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

SKILL

cloudlayer-automation

Name: cloudlayer-automation
Author: Composio

Automate Cloudlayer tasks via Rube MCP after checking current tool schemas.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

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

Summary

This skill appears to be a prompt-style wrapper with open-source hosting and strong community adoption, so the material alone indicates relatively low overall risk. However, its intended use depends on external Rube MCP and a Cloudlayer connection, which introduces remote tool discovery, connection management, and third-party authorization considerations during actual use.

CredentialsCaution

The material says the skill itself needs no API key, but the workflow requires creating a Cloudlayer connection via `RUBE_MANAGE_CONNECTIONS` and completing external authentication, implying credentials are delegated to or managed by Rube/Cloudlayer. There is no direct request for local secrets here, but third-party connection scopes and account privileges still warrant attention.

Network egressCaution

The README explicitly instructs users to add the remote MCP endpoint `https://rube.app/mcp` and use Composio/Rube to discover and execute Cloudlayer tools. Although the metadata says there are no remote endpoints, the documentation shows that queries, session data, and execution arguments are sent to Rube and related services, which is standard third-party network egress.

Code executionLow risk

Based on the provided material, the skill itself is a prompt/instruction wrapper and does not include local install scripts, shell commands, or direct host execution logic. Any execution capability appears to occur through external MCP/remote tools rather than granting local code execution.

Data accessCaution

The material does not indicate direct local file read/write by the skill itself, but `RUBE_SEARCH_TOOLS`, `RUBE_MULTI_EXECUTE_TOOL`, and `RUBE_REMOTE_WORKBENCH` can send task arguments, session information, and potentially business data to external tools. The effective data-access scope depends on the Cloudlayer tool schemas and the connected account permissions, which are not tightly bounded in the documentation.

Supply chainLow risk

The source is an open GitHub repository with very strong community adoption (~64.9k stars), which is a meaningful risk-reducing signal. The visible content is primarily README/skill instructions rather than a closed-source binary. The missing explicit license and unclear maintenance status are minor concerns but not enough on their own to justify a high-risk rating.

Recommendations

Before connecting to `https://rube.app/mcp`, review its privacy policy, logging, and data-handling practices.
Use least-privilege accounts when authorizing the Cloudlayer connection, and regularly review or revoke unused connections.
Inspect the actual schemas returned by `RUBE_SEARCH_TOOLS` before execution to avoid sending unnecessary sensitive data to external tools.
If used in production, validate the real operational scope of the Rube/Composio tools in an isolated account or test project first.

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 "cloudlayer-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/cloudlayer-automation/SKILL.md
2. Save it as ~/.claude/skills/cloudlayer-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

Cloudlayer Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/cloudlayer

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["cloudlayer"]
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 Cloudlayer-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `cloudlayer`
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 AI/ML API workflows via Rube MCP, checking latest tool schemas first.

ComposioGet→

$ loading_