What are the prerequisites?

Rube MCP must be connected, Baselinker connection must be ACTIVE, and you must run a tool search to fetch current schemas.

Why should I always search for tools first?

Tool schemas change frequently; hardcoding slugs can break workflows, so fetch current schemas before executing.

How should I handle sessions and pagination?

Reuse session IDs within a workflow, generate new IDs for new workflows, and check responses for pagination tokens to fetch all results.

baselinker-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Baselinker Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/baselinker

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Baselinker operations through Composio's Baselinker toolkit via Rube MCP. This skill emphasizes discovering current tool schemas before execution and requires an active Baselinker connection managed by RUBE_MANAGE_CONNECTIONS.

How This Skill Works

First, connect Rube MCP and verify that tool schemas can be retrieved. Then discover tools for your Baselinker task, check that the Baselinker connection is ACTIVE, and finally execute the chosen tool using a multi tool call with a memory object. The workflow relies on current tool schemas to ensure correct arguments and successful execution.

When to Use It

You need to fetch the latest Baselinker tool schemas before choosing a slug for automation.
You are integrating Baselinker actions into a multi step workflow that should reuse a session.
You must verify that the Baselinker connection is ACTIVE before running any tool.
You are executing tools that require exact field names and types from the current schema.
You are performing bulk Baselinker operations using a multi execute call and memory parameter.

Quick Start

Step 1: Add the Baselinker Rube MCP endpoint and verify connectivity (RUBE_SEARCH_TOOLS responds).
Step 2: Discover available Baselinker tools with RUBE_SEARCH_TOOLS to get slugs and schemas.
Step 3: Activate the Baselinker toolkit with RUBE_MANAGE_CONNECTIONS and run a tool with RUBE_MULTI_EXECUTE_TOOL, including memory and a session_id.

Best Practices

Always run tool discovery first to get current slugs and input schemas.
Check the Baselinker connection status and ensure it is ACTIVE prior to execution.
Honor exact field names and types from the tool schemas; avoid hardcoding.
Include a memory object in every multi tool execution call, even if empty.
Reuse session IDs within a workflow and create a new session only for new workflows; watch pagination tokens.

Example Use Cases

Sync ERP stock levels to Baselinker using a discovered tool slug and latest schema.
Export updated order statuses to Baselinker after processing payments.
Bulk update product pricing in Baselinker from a live data feed.
Create batch shipments in Baselinker from a daily manifest using discovered tools.
Run routine Baselinker validation and connectivity checks as part of a scheduled task.

Frequently Asked Questions

Add this skill to your agents