$ ~/registry/skill/composiohq-composio-skills-linkup-automation

SKILL

linkup-automation

Name: linkup-automation
Author: Composio

Automate Linkup tasks via Rube MCP after checking current tool schemas first.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

Prompt only, no code
Open source
Community-trusted· 64.9k

Summary

This skill is primarily a prompt-style workflow wrapper for Rube MCP/Composio. It does not request local secrets in the provided material and comes from a high-star open-source repository, so overall risk is relatively low. However, real use depends on a remote MCP service and third-party Linkup account connections, so external data flow and granted scopes should be verified and minimized.

CredentialsCaution

The material says the skill itself needs no API key, but it requires an active Linkup connection via `RUBE_MANAGE_CONNECTIONS` and an auth link flow. This implies credentials are handled by the external Rube/Linkup integration, creating normal third-party authorization and session exposure concerns, but no clear red flags of credential theft or unrelated secret collection are shown.

Network egressCaution

Although the metadata lists no remote host, the README explicitly instructs users to add `https://rube.app/mcp` as an MCP server and use Composio/Linkup-related services. In practice, tool discovery, connection status, and execution arguments will be sent to declared external endpoints. This is standard for remote automation tooling, and no suspicious unrelated domains are evident.

Code executionLow risk

The system flags this as `prompt-only`, and the material contains no install script, local shell execution, or instructions to spawn local processes. Its role is mainly to guide use of existing MCP tools rather than directly execute code on the host.

Data accessCaution

The skill text itself does not claim direct local file read/write access, but by invoking remote tools such as `RUBE_MULTI_EXECUTE_TOOL` and `RUBE_REMOTE_WORKBENCH`, it may process user-supplied business data, session IDs, tool arguments, and returned results. No excessive local file permissions are requested in the material, but the real data-access scope depends on the external tools and connected account permissions.

Supply chainLow risk

The source is an open GitHub repository with very strong community adoption (64.9k stars), which materially lowers supply-chain risk. The material also looks more like documentation/skill instructions than an executable artifact. Still, the license is unspecified and maintenance status is unknown, so recent repository activity and consistency with upstream Composio/Rube docs should be checked before production use.

Recommendations

Only connect to `rube.app/mcp` when needed, and verify its privacy, data-handling, and compliance posture.
Use least-privilege scopes during Linkup authorization, and periodically review or revoke unused connections and sessions.
Confirm the discovered Rube tool schemas and parameter meanings before execution to avoid sending sensitive data unnecessarily.
Before production use, review recent repository maintenance and cross-check behavior against official Composio documentation.

Audited by: gpt-5.4 · 2026-06-17

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "linkup-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/linkup-automation/SKILL.md
2. Save it as ~/.claude/skills/linkup-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

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

Automate Baselinker store and order workflows through Rube MCP tools.

ComposioGet→

$ loading_