How do I keep tool schemas up to date?

Always run RUBE_SEARCH_TOOLS first to fetch current schemas before choosing and executing a tool.

Is an ACTIVE Jobnimbus connection required?

Yes. Use RUBE_MANAGE_CONNECTIONS to verify the toolkit connection is ACTIVE before executing any tools.

Should I include memory in executions?

Yes. Always include a memory object in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.

jobnimbus-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Jobnimbus Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/jobnimbus

Prerequisites

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

Step 2: Check Connection

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

Overview

This skill automates Jobnimbus operations through Composio's Jobnimbus toolkit using Rube MCP. It emphasizes discovering current tool schemas before execution and validating an active Jobnimbus connection. By standardizing tool discovery and execution, it reduces manual steps and ensures up-to-date capabilities.

How This Skill Works

It begins by calling RUBE_SEARCH_TOOLS to fetch available Jobnimbus tools, input schemas, and recommended execution plans. It then checks the Jobnimbus connection with RUBE_MANAGE_CONNECTIONS and executes the chosen tool via RUBE_MULTI_EXECUTE_TOOL, supplying a memory object and the current session_id.

When to Use It

When automating a recurring Jobnimbus task (e.g., creating a record) to run via a workflow
When you need to perform a Jobnimbus operation only after verifying tool schemas have updated
When setting up a new Jobnimbus integration and validating connections first
When performing bulk Jobnimbus operations using discovered tool slugs
When reusing a session across multiple steps to improve efficiency

Quick Start

Step 1: Add the Rube MCP server (https://rube.app/mcp) to your client and confirm RUBE_SEARCH_TOOLS responds
Step 2: Establish a Jobnimbus connection with RUBE_MANAGE_CONNECTIONS and ensure the toolkit is active
Step 3: Discover a tool with RUBE_SEARCH_TOOLS and run it with RUBE_MULTI_EXECUTE_TOOL using the returned tool_slug and proper memory and session_id

Best Practices

Always call RUBE_SEARCH_TOOLS before executing to get current tool schemas
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before running tools
Use exact field names and types from the search results for tool arguments
Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty
Reuse session IDs within a workflow and generate new ones for separate runs

Example Use Cases

Automate creation of a Jobnimbus contact when a new lead arrives
Update a deal status in Jobnimbus after a triggered event from another system
Run a bulk import of tasks into Jobnimbus using discovered tool slugs
Sync notes from an external CRM into Jobnimbus via a mapped tool
Schedule a nightly cleanup of stale Jobnimbus records

Frequently Asked Questions

Add this skill to your agents