npm-automation

通过 Rube MCP 自动执行 NPM 安装、脚本运行与包管理流程。

来源

GitHub

更新于

2026-06-07

// 安全评估低风险

仅提示词，不执行代码
开源可审计

正在进行安全审计…

凭证密钥
网络外发
代码执行
数据访问
来源供应链

// 安装

复制安装指令，让 AI 自动完成配置 · 推荐新手

请帮我安装 askskill 上的 "npm-automation" 技能：
1. 下载 https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/npm-automation/SKILL.md
2. 保存为 ~/.claude/skills/npm-automation/SKILL.md
3. 装好后重载技能，告诉我可以用了

// 下载

下载 SKILL.md机读安装清单 ↗

// 用法示例

批量安装并运行脚本

输入

请通过 npm-automation 为这个 Node.js 项目执行依赖安装，然后运行 test 和 build 脚本；先搜索可用工具及其最新参数 schema，再按正确参数调用，并总结执行结果与报错。

预期产出

返回安装、测试和构建的执行结果摘要，并列出失败步骤与错误信息。

更新指定依赖版本

输入

请先搜索 npm 相关工具的当前 schema，然后将项目中的 eslint 和 typescript 更新到最新兼容版本，执行 npm install，并告诉我 package.json 与锁文件发生了哪些变化。

预期产出

输出依赖更新结果、相关文件变更说明，以及是否安装成功。

发布前检查流程

输入

请使用 npm-automation 先搜索工具 schema，再依次执行 npm ci、lint、test、build 和 npm pack，检查这个包是否具备发布条件，并汇总需要修复的问题。

预期产出

给出完整检查结果、发布准备状态，以及待修复问题清单。

// 文档

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`