How do I ensure tool schemas are current?

Always call RUBE_SEARCH_TOOLS before executing; it returns tool slugs, schemas, and known pitfalls.

Do I need API keys to use this skill?

No API keys are required—just configure the MCP endpoint (https://rube.app/mcp) and proceed.

How should I manage session IDs?

Reuse session IDs within a workflow for continuity, and generate new ones for new workflows; include session_id in requests and watch for pagination when discovering tools.

nano-nets-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Nano Nets Automation via Rube MCP

Automate Nano Nets operations through Composio's Nano Nets toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/nano_nets

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Nano Nets operations through Composio's Nano Nets toolkit via Rube MCP. It emphasizes discovering current tool schemas before executing and validating an active connection to ensure reliable automation.

How This Skill Works

Connect to the MCP server (https://rube.app/mcp), then Always call RUBE_SEARCH_TOOLS to fetch current Nano Nets tool slugs and schemas. Validate the connection with RUBE_MANAGE_CONNECTIONS, select a discovered tool slug, and execute it using RUBE_MULTI_EXECUTE_TOOL, including a memory object (even if empty) and reusing session IDs where appropriate.

When to Use It

When starting a Nano Nets workflow and you need up-to-date tool schemas before choosing an action
Before automation to verify that RUBE_MANAGE_CONNECTIONS shows an ACTIVE Nano Nets connection
When you want to run a discovered Nano Nets tool slug with its required arguments
For bulk or sequential operations using RUBE_MULTI_EXECUTE_TOOL or RUBE_REMOTE_WORKBENCH
When you need to handle tool discovery pagination to fetch all available tools

Quick Start

Step 1: Get Rube MCP: add https://rube.app/mcp as an MCP server in your client configuration
Step 2: Verify connectivity: run RUBE_SEARCH_TOOLS to confirm tool schemas are retrievable and MCP is responsive
Step 3: Discover and execute: pick a tool_slug from search results and call RUBE_MULTI_EXECUTE_TOOL with memory and session_id

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas and avoid hardcoding slugs or arguments
Check the connection status with RUBE_MANAGE_CONNECTIONS and proceed only if ACTIVE
Use exact field names and types from the tool search results to ensure schema compliance
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({})
Reuse session IDs within a single workflow and generate new ones for new workflows; watch for pagination tokens

Example Use Cases

Discover a Nano Nets task via RUBE_SEARCH_TOOLS and immediately execute it with RUBE_MULTI_EXECUTE_TOOL using the returned slug
Chain multiple Nano Nets tool executions in a single workflow by reusing a session_id across steps
Perform bulk Nano Nets operations with RUBE_REMOTE_WORKBENCH and run_composio_tool() for efficiency
Inspect full tool schemas using RUBE_GET_TOOL_SCHEMAS to validate required fields before execution
Implement pagination-aware tool discovery to fetch all available Nano Nets tools

Frequently Asked Questions

Add this skill to your agents