Customjs Automation via Rube MCP

Automate Customjs tasks via Rube MCP (Composio).

You say
Install this skill Read the source first Free Written by ComposioHQ · unverified publisher
Context cost
725 tokensestimated from the bundle, loaded when it triggers
Bundle
1 file · 2.9 kBtext throughout, nothing executable
Licence
free to use
Last change
no release on file
Servers it uses
1 serverrube

What it does

Automate Customjs tasks via Rube MCP (Composio). Always search tools first for current schemas.

Installed, it changes the agent in these ways.

What this skill changes about the agent is not written down here yet. The listing was collected from its source, and the description is in its own SKILL.md.

Workflow

Runs a procedure end to end.

browserautomationmcp

The skill itself

This is the whole product. A skill is instructions the model reads, so there is nothing behind the listing you cannot see first — the front matter loads with every session, and the body below it loads when the skill triggers.

SKILL.md2.9 kB · 92 lines
--- name: customjs-automation description: "Automate Customjs tasks via Rube MCP (Composio). Always search tools first for current schemas." requires: mcp: [rube] ---
8# Customjs Automation via Rube MCP
9
10Automate Customjs operations through Composio's Customjs toolkit via Rube MCP.
11
12**Toolkit docs**: [composio.dev/toolkits/customjs](https://composio.dev/toolkits/customjs)
13
14## Prerequisites
15
16- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
17- Active Customjs connection via RUBE_MANAGE_CONNECTIONS with toolkit customjs
18- Always call RUBE_SEARCH_TOOLS first to get current tool schemas
19
20## Setup
21
22**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.
23
241. Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
252. Call RUBE_MANAGE_CONNECTIONS with toolkit customjs
263. If connection is not ACTIVE, follow the returned auth link to complete setup
274. Confirm connection status shows ACTIVE before running any workflows
28
29## Tool Discovery
30
31Always discover available tools before executing workflows:
32
33```
34RUBE_SEARCH_TOOLS
35queries: [{use_case: "Customjs operations", known_fields: ""}]
36session: {generate_id: true}
37```
38
39This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls.
40
41## Core Workflow Pattern
42
43### Step 1: Discover Available Tools
44
45```
46RUBE_SEARCH_TOOLS
47queries: [{use_case: "your specific Customjs task"}]
48session: {id: "existing_session_id"}
49```
50
51### Step 2: Check Connection
52
53```
54RUBE_MANAGE_CONNECTIONS
55toolkits: ["customjs"]
56session_id: "your_session_id"
57```
58
59### Step 3: Execute Tools
60
61```
62RUBE_MULTI_EXECUTE_TOOL
63tools: [{
64 tool_slug: "TOOL_SLUG_FROM_SEARCH",
65 arguments: {/* schema-compliant args from search results */}
66}]
67memory: {}
68session_id: "your_session_id"
69```
70
71## Known Pitfalls
72
73- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling RUBE_SEARCH_TOOLS
74- **Check connection**: Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools
75- **Schema compliance**: Use exact field names and types from the search results
76- **Memory parameter**: Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({})
77- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows
78- **Pagination**: Check responses for pagination tokens and continue fetching until complete
79
80## Quick Reference
81
82| Operation | Approach |
83|-----------|----------|
84| Find tools | RUBE_SEARCH_TOOLS with Customjs-specific use case |
85| Connect | RUBE_MANAGE_CONNECTIONS with toolkit customjs |
86| Execute | RUBE_MULTI_EXECUTE_TOOL with discovered tool slugs |
87| Bulk ops | RUBE_REMOTE_WORKBENCH with run_composio_tool() |
88| Full schema | RUBE_GET_TOOL_SCHEMAS for tools with schemaRef |
89
90---
91*Powered by [Composio](https://composio.dev)*
92
In the file
SKILL.md372 words
Files1
Licence
Why you can read it

Nothing in a skill executes. The client loads the text and the model follows it, so a skill can be audited the way a runbook is — by reading it.

What it costs in context

Skills are not billed by the call. They are paid for in context: every token the instructions occupy is a token your code, your diff and your conversation cannot use. Here is what this one takes and when it takes it.

≈40
always loaded
The name and description, so the model knows the skill exists and when to reach for it.
685
on trigger
The instruction body, read only when the skill fires.
0.36%
of a 200k window
Ten skills this size would take about 4% of the window before you open a file.
050k100k150k200k context window

725 tokens, estimated from the bundle at four bytes to the token, held for the rest of the session once it triggers. Small enough to keep loaded permanently without thinking about it.

Servers bill, skills cost

A server charges by the month. A skill charges once per session, in context, and then keeps charging it for as long as the session lives.

Before and after

The same question, put to the same model twice: once as it comes, and once with these instructions loaded.

No worked example has been published for this skill yet.

Adoption
Installsnone yet
Ratingno reviews yet

The procedure it runs

The procedure has not been published here. It is in the skill’s own SKILL.md, which its author has not sent to the marketplace yet.

Prose, not code

These steps are written for a model to follow, not executed by a runtime. It can still be told to skip one, and it will say so when it does.

Servers it uses

It expects 1 MCP server to be connected. Each step names the tool it needs, so a missing server stops the skill with a plain message rather than an invented answer. They are not listed here yet — the names are the author’s own.

RUrubeNamed by the author; not listed in this catalogue, so connect it yourself.
What it asks for
Writes filesno
Network accessno

Read from the allowed-tools line of this skill’s own SKILL.md. A skill grants no permissions of its own — it can only ask for tools your client already has.

What it will not do

Every skill is narrow, and the useful ones say where they stop. These are the jobs this one is the wrong tool for.

What this skill is not for has not been published here. Nothing is implied by that: it is a section the author has not filled in.

What is in the bundle

1 file, 2.9 kB on disk. A bundle is text throughout: the instructions the model reads, plus the templates it fills in.

  • SKILL.md2.9 kB
What is not in it

No dependencies and nothing executable: a skill is text the agent reads, so the bundle is 1 file you can review in full before installing.

Install

Installing copies the bundle into your project. Nothing runs at install time — the files sit on disk until the model reads them.

# Customjs Automation via Rube MCP · 725 tokens when loaded npx mcprush@latest skill add composiohq/customjs-automation-via-rube-mcp

Writes to .claude/skills/customjs-automation-via-rube-mcp/ in the current project. Add --global to put it in your home directory instead, for every project.

Which clients pick it up on their own

A skill is a folder of text. A client with a skills folder reads it without being told; everywhere else the same text works, it is just handed to the model rather than found.

Claude Code.claude/skills/
Claude Desktop
ChatGPT
Cursor.cursor/skills/
VS Code.github/skills/
Codex CLI.agents/skills/
Gemini CLI.gemini/skills/
Grok.grok/skills/
Zed.agents/skills/
Windsurf.windsurf/skills/
Agent SDK.claude/skills/
HTTP / API
This release
Versionnot versioned
Publishedno release date on file
PriceFree
Referencecomposiohq/customjs-automation-via-rube-mcp

Versions

Its author publishes no version number, so there is nothing here to pin to: what you install is the folder as it stands today. Instructions change more often than APIs do — a skill can be rewritten entirely without anything it depends on moving.

v
  • No earlier releases have been published to the marketplace.
Pinning

Nothing to pin to: this skill carries no version number of its own. What you install is what the folder holds on the day you install it.

Reviews

no reviews yet · no installs yet

Nobody has reviewed this skill yet. The rating is the mean of the reviews written here, so there is none until somebody writes the first.

Who can post

Only accounts that have had the skill installed for fourteen days, so a review is written after living with it rather than after reading it. Publishers may reply once.

Publisher
Servers0
Claim this skill