What prerequisites must be satisfied before using linkup-automation?

Rube MCP must be connected, there must be an ACTIVE Linkup connection, and you must call RUBE_SEARCH_TOOLS to obtain current tool schemas.

Why is RUBE_SEARCH_TOOLS required every time?

Tool schemas change frequently; searching first ensures you use up-to-date tool_slugs and argument schemas.

Should I reuse sessions across steps?

Yes, reuse session IDs within a workflow to maintain continuity, but generate a new session for a new workflow to avoid cross-contamination.

linkup-automation

Scanned

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

Files (1)

SKILL.md

2.8 KB

Linkup Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/linkup

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Linkup operations through Composio's Linkup toolkit via Rube MCP. This requires a connected Rube MCP, an ACTIVE Linkup connection, and always calling RUBE_SEARCH_TOOLS first to fetch current tool schemas.

How This Skill Works

The workflow starts by discovering available Linkup tools with RUBE_SEARCH_TOOLS, then verifies an ACTIVE connection via RUBE_MANAGE_CONNECTIONS. Finally, tools are executed in a single workflow using RUBE_MULTI_EXECUTE_TOOL with the discovered tool slug, proper arguments, and memory, reusing sessions where appropriate.

When to Use It

You need to automate a specific Linkup operation end-to-end using a discovered tool slug.
You must ensure tool schemas are up-to-date before executing any Linkup workflow.
You want to reuse a session across multiple steps in a Linkup workflow.
You are executing multiple Linkup tools in a single workflow and require memory context.
You are troubleshooting or validating readiness by confirming ACTIVE connections before running Linkup tasks.

Quick Start

Step 1: Verify Rube MCP is reachable and run RUBE_SEARCH_TOOLS for Linkup use_case to fetch current tool schemas.
Step 2: Activate the Linkup connection with RUBE_MANAGE_CONNECTIONS toolkits: ["linkup"] and ensure status is ACTIVE.
Step 3: Execute a discovered tool using RUBE_MULTI_EXECUTE_TOOL with memory and the session_id from Step 2.

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas and avoid hardcoding slugs.
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools.
Use exact field names and types from the tool schemas returned by RUBE_SEARCH_TOOLS.
Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({}).
Reuse session IDs within a workflow to maintain continuity; create new sessions only for new workflows.

Example Use Cases

Automate a weekly Linkup data sync by discovering tools, connecting, and executing the data-sync tool in a single session.
Onboard a new user by discovering Linkup tasks, establishing a linkup connection, and sequencing tools for setup tasks.
Run a bulk Linkup update by executing multiple tools in one workflow with shared memory context.
Retry a failed Linkup task by re-discovering tools to capture any schema changes before re-running.
Audit and trace the execution path by reusing a session to document tool slugs and arguments used.

Frequently Asked Questions

Add this skill to your agents