What is Seqera automation via Rube MCP?

It automates Seqera tasks using Composio's Seqera toolkit through Rube MCP, enabling discovery, connection, and execution in a structured workflow.

Do I need API keys to use this skill?

No API keys are required. Just add the MCP server (e.g., https://rube.app/mcp) and use RUBE_SEARCH_TOOLS to fetch current tool schemas.

How do I handle changing tool schemas?

Always call RUBE_SEARCH_TOOLS to retrieve up-to-date tool slugs and input schemas, then use those values in RUBE_MULTI_EXECUTE_TOOL.

seqera-automation

Scanned

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

Files (1)

SKILL.md

2.8 KB

Seqera Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/seqera

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Seqera operations through Composio's Seqera toolkit via Rube MCP. Always search for current tool schemas before execution and verify the Seqera connection is ACTIVE to ensure repeatable, error-free workflows.

How This Skill Works

You first discover available Seqera tools and their input schemas with RUBE_SEARCH_TOOLS, then validate the Seqera connection using RUBE_MANAGE_CONNECTIONS, and finally execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL using the discovered slug, schema-compliant arguments, a memory payload, and a session_id.

When to Use It

Automating recurring Seqera tasks end-to-end by discovering tools, connecting, and executing with a single workflow.
When tool schemas change frequently and you must fetch current slugs and arg names before running tools.
When you need to validate an ACTIVE Seqera connection prior to tool execution.
When building multi-step workflows that reuse a session_id across steps (discover -> connect -> execute).
When performing batch or bulk Seqera runs using remote bench capabilities for efficiency.

Quick Start

Step 1: RUBE_SEARCH_TOOLS with use_case: 'Seqera operations' to discover available tools and input schemas.
Step 2: RUBE_MANAGE_CONNECTIONS with toolkits: ['seqera'] to establish or validate an ACTIVE connection.
Step 3: RUBE_MULTI_EXECUTE_TOOL with tool_slug from search results, proper arguments, memory: {}, and session_id: 'your_session_id'.

Best Practices

Always call RUBE_SEARCH_TOOLS first to get current tool slugs and input schemas.
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
Use exact field names and types from the search results; avoid hardcoding schemas.
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({}).
Reuse session IDs within a workflow and generate new ones for separate workflows.

Example Use Cases

Discover a Seqera tool slug via RUBE_SEARCH_TOOLS and execute it with the required arguments using RUBE_MULTI_EXECUTE_TOOL in a single session.
Schedule a weekly Seqera task: validate connection with RUBE_MANAGE_CONNECTIONS, then run the appropriate tool with stored session_id and memory.
Run multiple Seqera tools in sequence within the same session by reusing the session_id across successive RUBE_MULTI_EXECUTE_TOOL calls.
Bulk run multiple Seqera tasks using RUBE_REMOTE_WORKBENCH and run_composio_tool for batch processing.
Handle tool discovery pagination by repeatedly calling RUBE_SEARCH_TOOLS until all pages are retrieved before execution.

Frequently Asked Questions

Add this skill to your agents