Do I need API keys to use retailed-automation?

No API keys are required. You simply add the MCP server URL https://rube.app/mcp to your client configuration and proceed with the setup.

What must be verified before running a workflow?

Confirm that RUBE_SEARCH_TOOLS returns available tool slugs and that RUBE_MANAGE_CONNECTIONS shows ACTIVE for the retailed toolkit.

How important is memory in tool execution?

Memory must be included in every RUBE_MULTI_EXECUTE_TOOL call, even if empty, to preserve workflow state and context.

retailed-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Retailed Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/retailed

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["retailed"]
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 Retailed-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `retailed`
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/retailed-automation/SKILL.mdView on GitHub

Overview

Retailed-automation lets you orchestrate Retailed operations through Composio's Rube MCP toolkit. It emphasizes always discovering current tool schemas with RUBE_SEARCH_TOOLS before running workflows and ensuring an active Rube connection with the retailed toolkit. This approach reduces manual steps and ensures tools are invoked with up-to-date schemas.

How This Skill Works

It works by first discovering available tools using RUBE_SEARCH_TOOLS to fetch tool slugs and input schemas. Then it verifies the connection status with RUBE_MANAGE_CONNECTIONS for the retailed toolkit and, when active, executes the chosen tool via RUBE_MULTI_EXECUTE_TOOL, providing a memory payload and the required arguments. Always include memory and reuse session IDs as you progress through a workflow.

When to Use It

When you need current tool schemas before running a Retailed operation
When establishing or validating a Rube MCP connection for retailed
When executing a discovered Retailed tool with the exact input fields
When you must fetch all results from paginated tool responses
When reusing a session to streamline a sequence of Retailed tasks

Quick Start

Step 1: Verify RUBE_SEARCH_TOOLS is available and fetch current tool schemas
Step 2: Ensure the retailed connection is ACTIVE with RUBE_MANAGE_CONNECTIONS
Step 3: Execute a tool with RUBE_MULTI_EXECUTE_TOOL using the discovered slug and memory

Best Practices

Always call RUBE_SEARCH_TOOLS prior to any execution to get current schemas
Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools
Use exact field names and types from the search results
Include memory in RUBE_MULTI_EXECUTE_TOOL calls even if empty
Reuse session IDs within a workflow and create new ones for new runs

Example Use Cases

Automate monthly retailed inventory checks using discovered tools
Validate and activate a retailed connection, then execute a replenishment tool
Chain multiple retailed operations with RUBE_MULTI_EXECUTE_TOOL in a single session
Bulk run multiple retailed tools via RUBE_REMOTE_WORKBENCH for batch processing
Fetch complete results from paginated retailed tool queries using RUBE_SEARCH_TOOLS

Frequently Asked Questions

Add this skill to your agents