cloudlayer-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/cloudlayer-automation --openclawCloudlayer 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_CONNECTIONSwith toolkitcloudlayer - Always call
RUBE_SEARCH_TOOLSfirst 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_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkitcloudlayer - 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_CONNECTIONSshows ACTIVE status before executing tools - Schema compliance: Use exact field names and types from the search results
- Memory parameter: Always include
memoryinRUBE_MULTI_EXECUTE_TOOLcalls, 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
Source
git clone https://github.com/ComposioHQ/awesome-claude-skills/blob/master/composio-skills/cloudlayer-automation/SKILL.mdView on GitHub Overview
This skill automates Cloudlayer operations through Composio's Cloudlayer toolkit via Rube MCP. It emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS before running workflows to ensure up-to-date inputs and avoid hardcoded slugs.
How This Skill Works
Technically, you first discover available tools using RUBE_SEARCH_TOOLS to retrieve current slugs and input schemas. Then you verify the Cloudlayer connection with RUBE_MANAGE_CONNECTIONS and finally execute a tool via RUBE_MULTI_EXECUTE_TOOL using the discovered slug, appropriate arguments, a memory object, and a session_id. This pattern ensures schemas stay current and allows session reuse across a workflow.
When to Use It
- Automating routine Cloudlayer operations by selecting a tool slug from discovered results.
- Setting up or updating Cloudlayer workflows in response to new tool schemas or changes.
- Verifying an ACTIVE Cloudlayer connection before executing any tool.
- Performing bulk Cloudlayer operations using bulk execution or remote bench features.
- Fetching full tool schemas and adapting inputs to updated field names and types.
Quick Start
- Step 1: Ensure RUBE_SEARCH_TOOLS is available and the Cloudlayer connection is ACTIVE.
- Step 2: Use RUBE_SEARCH_TOOLS to discover tools for your Cloudlayer task and pick TOOL_SLUG_FROM_SEARCH.
- Step 3: Run RUBE_MULTI_EXECUTE_TOOL with the chosen tool slug, proper arguments, memory, and the session_id from Step 2.
Best Practices
- Always call RUBE_SEARCH_TOOLS first to obtain up-to-date tool slugs and input schemas.
- Check that RUBE_MANAGE_CONNECTIONS shows an ACTIVE status before execution.
- Use exact field names and types from the live search results; avoid hardcoding.
- Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
- Reuse session IDs within a workflow and generate new ones for new workflows.
Example Use Cases
- Automate a daily Cloudlayer backup by discovering the backup tool slug and running it with the required inputs.
- Connect to Cloudlayer via RUBE_MANAGE_CONNECTIONS and confirm ACTIVE before triggering a deployment workflow.
- Execute a Cloudlayer deployment step by pulling the tool slug from RUBE_SEARCH_TOOLS results and supplying correct arguments.
- Perform bulk Cloudlayer operations using RUBE_REMOTE_WORKBENCH to run multiple tools in sequence.
- Fetch full tool schemas with RUBE_GET_TOOL_SCHEMAS and adjust automation inputs accordingly.
