What is Rube MCP in this skill?

Rube MCP is the Composio MCP framework used to discover NPM tool schemas and execute them in a managed, stepwise workflow.

Why must I search tools first?

Tool schemas change over time; fetching current slugs and field names ensures correct execution.

What about session and memory handling?

Reuse session IDs within a workflow for continuity and always include a memory object in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.

npm-automation

Scanned

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

Files (1)

SKILL.md

2.8 KB

NPM Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/npm

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate NPM operations using Composio's Rube MCP toolkit. This skill orchestrates discovery of current NPM tool schemas, validates an active connection, and executes tools to streamline npm workflows.

How This Skill Works

First, discover available NPM tools with RUBE_SEARCH_TOOLS. Then verify or establish an ACTIVE npm connection with RUBE_MANAGE_CONNECTIONS. Finally, execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL, supplying the discovered tool_slug and a memory object, and reuse session IDs within the workflow.

When to Use It

You want to automate a specific NPM operation (install, audit, publish, etc.) without manual steps.
Tool schemas change over time and you need up-to-date slugs and arguments before running tasks.
Orchestrating multiple NPM tasks in a single, reusable workflow across projects.
Setting up a reusable automation for routine NPM maintenance (cache clean, prune, audit).
Performing bulk NPM operations across several repositories in a controlled session.

Quick Start

Step 1: RUBE_SEARCH_TOOLS with queries: [{use_case: "NPM operations"}] to discover available tools.
Step 2: RUBE_MANAGE_CONNECTIONS with toolkits: ["npm"] and a session_id; ensure status is ACTIVE.
Step 3: RUBE_MULTI_EXECUTE_TOOL with the chosen tool_slug, memory: {}, and the session_id from Step 2.

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas and avoid hardcoding slugs.
Verify that the NPM connection is ACTIVE via RUBE_MANAGE_CONNECTIONS before execution.
Use the exact field names and types returned by the tool schemas from the search results.
Always include a memory object in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({}).
Reuse session IDs within a workflow and generate new ones for new workflows; watch for pagination tokens in responses.

Example Use Cases

Install and update dependencies across multiple projects by discovering and executing the appropriate NPM tool slugs.
Run npm audit and automatically apply fixes using a discovered tool with memory tracking for state.
Publish a package by selecting the correct publish tool slug from live schemas and executing with required arguments.
Clear NPM cache and prune outdated packages across a repository fleet in a single workflow.
Batch update dependencies in several repos by orchestrating multiple tool executions within one session.

Frequently Asked Questions

Add this skill to your agents