customjs-automation

Automate Customjs operations through the Rube MCP gateway for integrated task execution.

74.2k|8.5k|Updated Oct 17, 2025
One-click install
npx skills add https://github.com/ComposioHQ/awesome-claude-skills --skill customjs-automation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: customjs-automation
Source: https://github.com/ComposioHQ/awesome-claude-skills/tree/main/composio-skills/customjs-automation
Command: npx skills add https://github.com/ComposioHQ/awesome-claude-skills --skill customjs-automation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the complexity of managing Customjs tasks by providing a standardized, automated interface for tool discovery, connection management, and execution via the Rube MCP gateway.

Core Features & Use Cases

  • Tool Discovery: Dynamically fetch current tool schemas and execution plans to ensure compatibility.
  • Connection Management: Verify and maintain active connections to Customjs toolkits.
  • Multi-Execution: Perform complex, multi-step workflows using discovered tools and session-based memory.
  • Use Case: Automate repetitive Customjs operations by chaining tool discovery, connection verification, and multi-tool execution in a single session.

Quick Start

Use the customjs-automation skill to discover available tools and execute a specific task workflow for your current session.

Frequently Asked Questions about customjs-automation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I discover available Customjs tools?

Call the RUBE_SEARCH_TOOLS function with a specific use case query to retrieve available tool slugs, input schemas, and recommended execution plans.

How to verify if my Customjs connection is active?

Use the RUBE_MANAGE_CONNECTIONS function with the 'customjs' toolkit parameter to check the current connection status and initiate authentication if required.

Can I reuse session IDs for multiple workflows?

It is recommended to reuse session IDs within a single logical workflow for state consistency, but you should generate new session IDs for distinct, unrelated workflows.

Why must I call RUBE_SEARCH_TOOLS before executing?

Tool schemas and slugs are subject to change; calling RUBE_SEARCH_TOOLS ensures you are using the most current, valid arguments and preventing execution errors.

What is the purpose of the memory parameter in RUBE_MULTI_EXECUTE_TOOL?

The memory parameter is a required field for state tracking during multi-tool execution; it should be included in every call, even if passed as an empty object.