How do I ensure current tool schemas?

Always call RUBE_SEARCH_TOOLS first; this returns tool slugs, input schemas, and execution plans.

What if the connection isn't ACTIVE?

Follow the returned auth link to complete setup, then re-check until ACTIVE.

How do I run multiple tools in sequence?

Use RUBE_MULTI_EXECUTE_TOOL with memory and session_id, reusing session IDs within a workflow, and discover tools before each run to avoid hard-coded references.

storeganise-automation

Scanned

npx machina-cli add skill ComposioHQ/awesome-claude-skills/storeganise-automation --openclaw

Files (1)

SKILL.md

2.9 KB

Storeganise Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/storeganise

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["storeganise"]
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 Storeganise-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `storeganise`
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/storeganise-automation/SKILL.md

View on GitHub

Overview

Automate Storeganise operations using Composio's Storeganise toolkit through Rube MCP. This approach keeps tool schemas current by always calling RUBE_SEARCH_TOOLS before execution, avoiding hard-coded slugs. It requires a connected Rube MCP, an active Storeganise connection, and session-aware workflows.

How This Skill Works

Technically, you first discover available Storeganise tools with RUBE_SEARCH_TOOLS to obtain up-to-date slugs and input schemas. Then you establish an active connection via RUBE_MANAGE_CONNECTIONS for the storeganise toolkit. Finally, you execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL, passing the schema-compliant arguments, memory, and a session_id; always reuse sessions when appropriate and do not hardcode tool slugs.

When to Use It

Setting up a new Storeganise automation workflow and adapting to changing tool schemas.
Scheduling recurring Storeganise tasks where schemas may change over time.
Verifying the active connection before running any workflows.
Executing multiple tools in a batch with RUBE_MULTI_EXECUTE_TOOL, ensuring memory and proper session reuse.
Diagnosing issues by re-discovering tools to avoid stale hard-coded references.

Quick Start

Step 1: Discover available Storeganise tools with RUBE_SEARCH_TOOLS for Storeganise operations.
Step 2: Establish and verify the Storeganise connection with RUBE_MANAGE_CONNECTIONS for the storeganise toolkit.
Step 3: Execute the chosen tool using RUBE_MULTI_EXECUTE_TOOL with the discovered tool_slug, proper arguments, memory, and a session_id.

Best Practices

Always run RUBE_SEARCH_TOOLS first to fetch current tool schemas.
Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE before execution.
Use exact field names and types from the search results; avoid hardcoding.
Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty.
Reuse session IDs within a workflow and handle pagination if present.

Example Use Cases

Automate a weekly stock check in Storeganise using a discovered tool slug and dynamic arguments.
Create an order import workflow that maps Storeganise fields to your store's data model using current schemas.
Bulk update product metadata across many items via RUBE_REMOTE_WORKBENCH run_composio_tool.
Reconnect after schema changes and verify ACTIVE before running the next step.
Handle large result sets with pagination by continuing fetches using RUBE_SEARCH_TOOLS outputs to drive next queries.

Frequently Asked Questions

Add this skill to your agents