What are the prerequisites for neutrino-automation?

Rube MCP must be connected, RUBE_SEARCH_TOOLS must respond, and an active Neutrino connection via RUBE_MANAGE_CONNECTIONS with toolkit neutrino.

Why do I need to search tools first?

Tool schemas change over time. Searching tools ensures you use current tool slugs and argument schemas rather than hardcoding values.

How do I validate connection before running?

After configuring the neutrino toolkit, call RUBE_MANAGE_CONNECTIONS and ensure the status is ACTIVE before executing any tools.

neutrino-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Neutrino Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/neutrino

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Neutrino operations via Composio's Neutrino toolkit through Rube MCP. Always fetch current tool schemas before running workflows.

How This Skill Works

First connect to Rube MCP and confirm RUBE_SEARCH_TOOLS responds. Then discover available neutrino tools for your task and verify an ACTIVE Neutrino connection. Finally execute the selected tool with RUBE_MULTI_EXECUTE_TOOL, including memory and session_id as required by the schema.

When to Use It

End-to-end Neutrino workflow automation using dynamically discovered tool schemas.
Tool schemas change frequently; you must search tools first before execution.
You need to verify that the Neutrino connection is ACTIVE before running tools.
You want to reuse a session ID for multi-step neutrino workflows.
Perform batch or bulk neutrino tasks via remote bench when applicable.

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
Step 2: Verify RUBE_SEARCH_TOOLS responds to confirm MCP connectivity and current tool schemas.
Step 3: Call RUBE_MANAGE_CONNECTIONS with toolkits: ["neutrino"]. If the connection is not ACTIVE, follow the returned auth link to complete setup, then confirm ACTIVE before running any workflows.

Best Practices

Always call RUBE_SEARCH_TOOLS before executing tools to get current slugs and schemas.
Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE status before running tools.
Use exact field names and types from the search results instead of hardcoding.
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
Reuse session IDs within a workflow and generate new ones for new runs; watch for pagination tokens.

Example Use Cases

Discover tool slugs for a Neutrino operation with RUBE_SEARCH_TOOLS and run using RUBE_MULTI_EXECUTE_TOOL.
Connect the neutrino toolkit with RUBE_MANAGE_CONNECTIONS and execute a tool per its schema.
Implement a multi-step neutrino workflow by reusing a session_id and passing memory.
Use RUBE_REMOTE_WORKBENCH to bulk run composio tools for several neutrino tasks.
Fetch the full tool schemas with RUBE_GET_TOOL_SCHEMAS and execute with the discovered schemaRef.

Frequently Asked Questions

Add this skill to your agents