storerocket-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/storerocket-automation --openclawStorerocket Automation via Rube MCP
Automate Storerocket operations through Composio's Storerocket toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/storerocket
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Storerocket connection via
RUBE_MANAGE_CONNECTIONSwith toolkitstorerocket - 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 toolkitstorerocket - 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: "Storerocket 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 Storerocket task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["storerocket"]
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 Storerocket-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit storerocket |
| 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/storerocket-automation/SKILL.mdView on GitHub Overview
Automate Storerocket operations through Composio's Storerocket toolkit using Rube MCP. Always fetch up-to-date tool schemas with RUBE_SEARCH_TOOLS before running workflows, and ensure an ACTIVE Storerocket connection to execute tools reliably.
How This Skill Works
The workflow starts by discovering available Storerocket tools with RUBE_SEARCH_TOOLS to get current tool slugs and input schemas. Next, verify the connection using RUBE_MANAGE_CONNECTIONS for the storerocket toolkit, then execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL, including a memory object. Tool schemas dictate exact argument names and types, so avoid hardcoding slugs or fields and rely on the discovered schema.
When to Use It
- Automating routine Storerocket tasks (e.g., data sync or job triggers) to save time.
- When tool schemas change or new tools are added and you must adapt workflows.
- Before executing workflows, ensure an ACTIVE connection is established for the storerocket toolkit.
- Orchestrating multi-step workflows that involve several Storerocket tools in sequence.
- Handling tasks with pagination or reusing session IDs across steps within a workflow.
Quick Start
- Step 1: Get Rube MCP configured and confirm RUBE_SEARCH_TOOLS responds with Storerocket tool slugs.
- Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkit 'storerocket' and ensure the session shows ACTIVE.
- Step 3: Discover a tool with RUBE_SEARCH_TOOLS, then execute it with RUBE_MULTI_EXECUTE_TOOL using the discovered slug and memory parameter.
Best Practices
- Always run RUBE_SEARCH_TOOLS first to obtain current tool slugs and input schemas.
- Verify RUBE_MANAGE_CONNECTIONS reports ACTIVE before executing any tool.
- Use exact field names and types from the discovered tool schemas; do not hardcode values.
- Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if it is an empty object ({}).
- Reuse session IDs within a workflow and fetch pagination tokens as needed until completion.
Example Use Cases
- Set up a recurring data import into Storerocket by discovering the relevant data_sync tool and executing it with the latest required arguments.
- Coordinate a multi-step update: discover tools, validate the connection, then run several tools in sequence within a single session.
- Perform bulk operations using RUBE_REMOTE_WORKBENCH with run_composio_tool() for parallelized Storerocket tasks.
- Query the full tool schema with RUBE_GET_TOOL_SCHEMAS and map each tool_slug to its schemaRef-guided fields before execution.
- Handle large result sets by utilizing pagination tokens returned from RUBE_SEARCH_TOOLS and continuing discovery until complete.
