home / skills / composiohq / awesome-claude-skills / baselinker-automation

baselinker-automation skill

safe

/baselinker-automation

This skill helps automate Baselinker tasks using Rube MCP, ensuring tool discovery and active connections before executing workflows.

npx playbooks add skill composiohq/awesome-claude-skills --skill baselinker-automation

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

2.9 KB

---
name: baselinker-automation
description: "Automate Baselinker tasks via Rube MCP (Composio). Always search tools first for current schemas."
requires:
  mcp: [rube]
---

# Baselinker Automation via Rube MCP

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

**Toolkit docs**: [composio.dev/toolkits/baselinker](https://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.

1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `baselinker`
3. If connection is not ACTIVE, follow the returned auth link to complete setup
4. 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](https://composio.dev)*

Overview

This skill automates Baselinker tasks through Rube MCP using the Composio Baselinker toolkit. It provides a repeatable pattern for discovering tool schemas, validating connections, and executing operations safely. The skill emphasizes dynamic discovery so workflows remain robust as tool schemas change.

How this skill works

Before any operation it calls RUBE_SEARCH_TOOLS to retrieve current tool slugs, input schemas, and execution plans. It then verifies the Baselinker connection via RUBE_MANAGE_CONNECTIONS and runs actions with RUBE_MULTI_EXECUTE_TOOL (including a memory object and session_id). For bulk or remote flows you can use RUBE_REMOTE_WORKBENCH and run_composio_tool(), and RUBE_GET_TOOL_SCHEMAS exposes full schema details when needed.

When to use it

Automate order, product, or inventory tasks in Baselinker at scale
Integrate Baselinker actions into multi-step agent workflows or pipelines
Run bulk operations where remote workbench orchestration is required
When tool schemas may change frequently and you need a schema-driven approach
When you must ensure connection state before executing operations

Best practices

Always call RUBE_SEARCH_TOOLS first — never hardcode tool slugs or arguments
Confirm RUBE_MANAGE_CONNECTIONS shows ACTIVE for the baselinker toolkit before running tools
Pass an explicit memory object in RUBE_MULTI_EXECUTE_TOOL calls (use {} if empty)
Reuse session_id within a workflow; generate a new one for separate workflows
Follow exact field names and types from the search results and handle pagination tokens

Example use cases

Discover available Baselinker actions and their input schemas for a new integration
Validate and activate a Baselinker connection before running daily sync jobs
Execute a multi-step order processing flow by chaining RUBE_MULTI_EXECUTE_TOOL calls with the discovered tool slugs
Run bulk updates to inventory or product listings via RUBE_REMOTE_WORKBENCH and run_composio_tool()
Fetch full tool schemas with RUBE_GET_TOOL_SCHEMAS to build UI forms that match backend expectations

FAQ

Do I need API keys to use Rube MCP?

No API keys are required; add https://rube.app/mcp as an MCP server in your client configuration to connect.

What happens if I skip RUBE_SEARCH_TOOLS?

Skipping search risks using outdated slugs or wrong input shapes, causing failures. Always search first to get current schemas.

Is session_id required?

Yes — reuse a session_id throughout a workflow for consistent context and generate a new one for separate workflows.