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

SKILL

nango-automation

Name: nango-automation
Author: Composio

Automate Nango workflows via Rube MCP using current tool schemas first.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

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

Summary

This skill appears to be an open-source prompt-only wrapper that instructs users to operate Nango via Rube MCP/Composio; no local execution, embedded secrets, or direct file access is described. The main security consideration is reliance on external MCP services and third-party connection authorization, so network egress and external credential handling deserve attention, but no concrete high-risk red flags are evident from the provided materials.

CredentialsCaution

The materials say the skill itself requires “no API keys,” but the workflow depends on `RUBE_MANAGE_CONNECTIONS` to establish an ACTIVE Nango connection and complete an returned auth link, implying credentials are likely handled or exchanged by Rube/Composio/Nango. No local plaintext secret requirement is shown, but the scope and storage of third-party OAuth/connection tokens should be reviewed.

Network egressCaution

The README explicitly requires connecting to the remote MCP endpoint `https://rube.app/mcp` and executing operations through Composio’s Nango toolkit; this means user requests, tool arguments, and some context may be sent to Rube/Composio and related integration paths. This outbound traffic is consistent with the stated function and is a normal capability, but the materials do not detail data flows, retention, or the precise recipient boundary.

Code executionLow risk

Based on the provided materials, this is a prompt/instructional skill and does not describe spawning local processes, running scripts, installing binaries, or invoking system commands. Its core behavior is to guide MCP tool usage, so no additional local code-execution privilege is evident.

Data accessLow risk

The materials do not claim direct read/write access to local files, clipboard, databases, or other host resources; the access scope appears centered on connected Nango/Composio tool capabilities. From the skill text itself, there is no sign of excessive local data access.

Supply chainLow risk

The source is an open GitHub repository with strong community trust (64.7k stars), which materially lowers supply-chain risk; it is also marked prompt-only, making it easier to review. That said, the license is undeclared and maintenance status is unknown, so repository activity and commit provenance should still be checked.

Recommendations

Before connecting to `rube.app/mcp`, verify its privacy policy, retention practices, and the data-flow boundary between Rube, Composio, and Nango.
Use least-privilege authorization for Nango connections created via `RUBE_MANAGE_CONNECTIONS`, and regularly rotate or revoke unused connections.
Test with low-sensitivity data first in production-like setups to confirm that `RUBE_SEARCH_TOOLS` and subsequent tool execution do not expose more business content than expected.
Review actual repository maintenance activity, contributor trustworthiness, and license terms before adopting it in a formal workflow.

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

// download

Download SKILL.mdInstall manifest ↗

// docs

Nango Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/nango

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["nango"]
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 Nango-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `nango`
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 API Ninjas tasks via Rube MCP with schema-first tool discovery.

ComposioGet→

$ loading_