Why must I always search tools first?

Tool schemas change. Never hardcode tool slugs or arguments without calling RUBE_SEARCH_TOOLS.

What is required when executing tools?

Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty, and ensure the session_id is provided.

productlane-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Productlane Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/productlane

Prerequisites

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

Step 2: Check Connection

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

View on GitHub

Overview

Automate Productlane operations by connecting Composio's Rube MCP to the Productlane toolkit. It streamlines task execution by discovering current tool schemas before each run, ensuring a valid Active connection, and executing tools in structured workflows.

How This Skill Works

Technically, you first verify MCP availability using RUBE_SEARCH_TOOLS, then establish or refresh a Productlane connection with RUBE_MANAGE_CONNECTIONS. Once tools are discovered, you execute them with RUBE_MULTI_EXECUTE_TOOL using the returned tool_slug and a memory payload, within an active session_id.

When to Use It

Automate repetitive Productlane tasks without hardcoding tool slugs.
Always fetch current tool schemas before running to avoid broken integrations.
Run multi-step workflows that reuse a session_id for efficiency.
Perform bulk Productlane operations via run_composio_tool or multi-execute workflows.
Confirm the Productlane connection is ACTIVE and complete any required auth flow before execution.

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client configuration and verify availability with RUBE_SEARCH_TOOLS.
Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkits: ["productlane"] and complete any auth flow if the connection is not ACTIVE.
Step 3: Discover tools with RUBE_SEARCH_TOOLS for your Productlane use case, then execute a tool via RUBE_MULTI_EXECUTE_TOOL using the provided tool_slug, memory, and a session_id.

Best Practices

Always search tools first; tool schemas change.
Verify connection status is ACTIVE before running tools.
Use exact field names and types from the search results (schema compliance).
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({}).
Reuse session IDs within a workflow and manage pagination tokens when present.

Example Use Cases

Discover tools for a specific Productlane task and execute one tool in an ACTIVE session.
Use RUBE_MULTI_EXECUTE_TOOL to perform a sequence of Productlane operations with a single session.
Bulk update multiple Productlane items using RUBE_REMOTE_WORKBENCH or run_composio_tool.
Fetch the full tool schemas with RUBE_GET_TOOL_SCHEMAS before a critical change to ensure correct args.
Recover from a non-ACTIVE connection by following the auth link, then retry the workflow.

Frequently Asked Questions

Add this skill to your agents