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

SKILL

neutrino-automation

Name: neutrino-automation
Author: Composio

Automate Neutrino tasks via Rube MCP with schema lookup first.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

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

Summary

Overall risk is relatively low. The skill itself appears to be an open-source prompt/instruction wrapper, but its real functionality depends on external Rube MCP and a Neutrino connection, so data access and network egress occur through those external services and should be verified before use.

CredentialsCaution

The material says the skill itself needs no API keys, but the README also requires an ACTIVE `neutrino` connection via `RUBE_MANAGE_CONNECTIONS` and may redirect users to an auth link. This means the skill does not directly collect local secrets, yet real use still depends on external account authorization, so OAuth/connection token scope and misuse risk should be reviewed.

Network egressCaution

The README explicitly instructs adding `https://rube.app/mcp` as an MCP server and using Composio/Rube to access Neutrino tools; queries, execution arguments, session IDs, and related business data may be sent through that path. No clearly suspicious exfiltration beyond the stated purpose is shown, but this is a definite third-party network dependency.

Code executionLow risk

Based on the provided material, this is a prompt-only skill/usage guide and does not include local install scripts, shell commands, or requirements to spawn local processes. The README discusses calling existing MCP tools and a remote workbench rather than directly requesting local system execution privileges.

Data accessCaution

The skill claims to automate Neutrino operations and uses Rube/Composio to discover and execute Neutrino tools; this means effective data access depends on the permissions granted to the Neutrino connection and the selected tool schemas. No excessive local file access is shown, but the scope of external account operations is not transparent and should be limited by least privilege.

Supply chainCaution

Positive factors include a GitHub source, visible open-source content, and strong community adoption (64.7k stars), all of which materially reduce risk. However, the repository license is not stated, maintenance status is unknown, and real functionality depends on external Rube MCP/Composio services rather than code that can be fully audited from the repo alone, so this is better rated as caution rather than high risk.

Recommendations

Before connecting to `rube.app/mcp`, verify its privacy policy, logging retention, and data handling scope.
Grant the Neutrino connection only the minimum required permissions and regularly review callable tools and account scope.
Avoid placing unnecessary sensitive data in tool queries, execution arguments, or memory/session fields.
Verify repository maintenance, release history, and external service terms before using it in production.

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 "neutrino-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/neutrino-automation/SKILL.md
2. Save it as ~/.claude/skills/neutrino-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

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

Automate Moz SEO tasks via Rube MCP using current tool schemas first.

ComposioGet→

$ loading_