$ ~/registry/skill/composiohq-composio-skills-jobnimbus-automation

SKILL

jobnimbus-automation

Name: jobnimbus-automation
Author: Composio

Automate Jobnimbus tasks and workflows through Rube MCP for faster operations.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

Prompt only, no code
Open source
Community-trusted· 64.7k

Summary

The skill material itself is an open-source prompt-style guide with no shown local secrets requirement or local code execution, so overall risk is low. Caution is still warranted because it depends on remote Rube MCP and an external Jobnimbus connection, where actual data access and egress occur through third-party services.

CredentialsCaution

The material says the skill needs 'no API keys', but actual use requires establishing a `jobnimbus` connection via `RUBE_MANAGE_CONNECTIONS` and completing external authentication, which suggests credentials are likely brokered by Rube/Composio rather than absent; watch for third-party token handling and least-privilege scope.

Network egressCaution

The README explicitly requires adding the remote MCP endpoint `https://rube.app/mcp` and operating through Composio's Jobnimbus toolkit; user task content, tool arguments, and potentially business data will be sent to Rube/Composio and Jobnimbus-related services. This is expected egress, not a specific red flag in the material.

Code executionLow risk

Per the provided checks, this is a prompt-only skill document; the material does not declare spawning local processes, running scripts, or requesting system-level permissions. Its role is to guide use of existing MCP tools rather than shipping executable code.

Data accessCaution

The skill itself does not claim local file access, but its purpose is to automate Jobnimbus operations through a remote toolkit, which may read or modify business data in Jobnimbus such as customers or jobs; this is within stated functionality, so review whether the connected account has overly broad permissions.

Supply chainLow risk

The source is a GitHub open-source repository with strong stated community adoption (64.7k stars), both of which materially reduce risk; the current material is mainly documentation, so auditability is comparatively good. The undeclared license and unknown maintenance status are worth noting but do not alone make it high risk.

Recommendations

Before enabling it, verify the data handling, log retention, and token custody policies of Rube/Composio and Jobnimbus.
Use a least-privilege Jobnimbus account for the connection and avoid granting unnecessary read/write scope.
Validate `RUBE_SEARCH_TOOLS` and execution behavior with test data before touching production records.
Allowlist approved MCP endpoints only, such as verified `rube.app` domains, and monitor outbound requests.

Audited by: gpt-5.4 · 2026-06-17

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "jobnimbus-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/jobnimbus-automation/SKILL.md
2. Save it as ~/.claude/skills/jobnimbus-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

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

Automate Workiom tasks and streamline workflow updates through Rube MCP.

ComposioGet→

$ loading_