Do I need API keys for Ncscale automation?

No. Add the MCP server (e.g., https://rube.app/mcp) and use RUBE_SEARCH_TOOLS to fetch current tool schemas.

What if tool schemas change?

Always run RUBE_SEARCH_TOOLS to fetch updated slugs and field names before execution; never hardcode.

How do I verify readiness before running a workflow?

Check that RUBE_MANAGE_CONNECTIONS reports an ACTIVE status and that you have a valid session_id before RUBE_MULTI_EXECUTE_TOOL; include memory.

ncscale-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Ncscale Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/ncscale

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Ncscale operations through Composio's Ncscale toolkit via Rube MCP. This skill orchestrates tool discovery, connectivity, and execution to run Ncscale workflows end-to-end. It emphasizes searching for current schemas first to avoid outdated tool slugs.

How This Skill Works

It starts by calling RUBE_SEARCH_TOOLS to fetch Ncscale tool slugs and schemas. Then it uses RUBE_MANAGE_CONNECTIONS to establish or verify a Ncscale toolkit connection and checks that the status is ACTIVE. Finally, it runs RUBE_MULTI_EXECUTE_TOOL with the discovered tool slug, the required memory field, and a session_id to execute the workflow.

When to Use It

When you need end-to-end Ncscale automation using up-to-date tool schemas
When tool schemas may change and you must fetch current slugs before running
When linking and validating a Ncscale connection via Rube MCP before execution
When executing multiple Ncscale tools in a single session with memory retention
When troubleshooting automation by re-discovering tools and rechecking connections

Quick Start

Step 1: Ensure Rube MCP is connected and run RUBE_SEARCH_TOOLS to load current Ncscale schemas
Step 2: Use RUBE_MANAGE_CONNECTIONS to connect to toolkit ncscale and confirm ACTIVE
Step 3: Execute a tool with RUBE_MULTI_EXECUTE_TOOL using the discovered slug, proper memory, and a session_id

Best Practices

Always call RUBE_SEARCH_TOOLS before executing to get current tool slugs and schemas
Verify the connection is ACTIVE with RUBE_MANAGE_CONNECTIONS before running tools
Use exact field names and types from search results; avoid hardcoding slugs/args
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
Reuse session IDs within a workflow and create new ones for separate workflows

Example Use Cases

Discover a Ncscale tool with RUBE_SEARCH_TOOLS and execute it via RUBE_MULTI_EXECUTE_TOOL using the returned slug and schema
Set up a scheduled Ncscale workflow by connecting to ncscale, discovering tools, and running a single tool on a timer
Batch run several Ncscale tools in one session, preserving state with memory and a shared session_id
Adapt automation when tool schemas update by re-running tool discovery and updating execution parameters
Troubleshoot failures by verifying ACTIVE connections and re-fetching tool schemas before retrying

Frequently Asked Questions

Add this skill to your agents