Customjs Automation via Rube MCP

SkillSearch

Once added, your AI can automate Customjs tasks on your behalf. It works out which Customjs tool fits your request, checks the latest details about that tool, and runs it for you. You describe what you want done, and it takes care of the Customjs side.

Instructions available. Your AI can read the instructions. Execution depends on the setup they require.

Account requirements not reviewed. Check the skill instructions before use; ahel provides instructions and does not run this skill.

After adding it, describe the Customjs task you want done in plain language. Your AI will find and run the right Customjs tool from there.

Then ask your AI: use the Customjs Automation via Rube MCP skill

What your AI can do with it

Automate Customjs tasks from a plain-language request
Discover the right Customjs tool for a task on its own
Run Customjs tools without manual setup
Check the latest tool details before running anything

What this skill tells your AI

The instructions your AI receives, as published by composio-community/awesome-codex-skills in composio-skills/customjs-automation/SKILL.md and read by ahel’s review.

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

Toolkit docs: composio.dev/toolkits/customjs

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["customjs"]
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 Customjs-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `customjs`
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

Signals

GitHub stars: 17k
Forks: 2k
Last commit: Jul 2026

Others that do the same job

customjs-automation
Skill · composiohq

Advanced

Item type: skill
Key: customjs-automation
Source: github.com/composio-community/awesome-codex-skills

github.com/composio-community/awesome-codex-skills