How do I start automating Entelligence tasks?

Add the Rube MCP endpoint, verify RUBE_SEARCH_TOOLS, establish an ACTIVE entelligence connection with RUBE_MANAGE_CONNECTIONS, then use RUBE_MULTI_EXECUTE_TOOL with a discovered tool slug and the required arguments.

What if tool schemas change?

Always run RUBE_SEARCH_TOOLS to fetch current schemas before executing tools; do not hardcode slugs or arguments to avoid failures.

Do I need API keys to use Entelligence on MCP?

No API keys are required. You only need to add the MCP server and ensure the Entelligence toolkit connection is ACTIVE.

entelligence-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Entelligence Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/entelligence

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["entelligence"]
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 Entelligence-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `entelligence`
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/entelligence-automation/SKILL.md

View on GitHub

Overview

Automate Entelligence tasks through Composio's Entelligence toolkit using Rube MCP. The approach emphasizes always searching for current tool schemas before running workflows to avoid outdated slugs and arguments.

How This Skill Works

RUBE_SEARCH_TOOLS fetches available Entelligence tools and their input schemas. RUBE_MANAGE_CONNECTIONS ensures the entelligence toolkit connection is ACTIVE. When ready, RUBE_MULTI_EXECUTE_TOOL runs the chosen tool with exact arguments, memory, and session_id.

When to Use It

When you need up-to-date Entelligence tool schemas before automation
When automating recurring Entelligence tasks with a consistent workflow
When you must validate that the Entelligence connection is ACTIVE before execution
When discovering tools to choose the right tool slug and execution plan
When handling pagination and fetching multiple Entelligence tool schemas

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client configuration
Step 2: Verify RUBE_SEARCH_TOOLS responds to confirm tool availability
Step 3: Run RUBE_MANAGE_CONNECTIONS with toolkits: ["entelligence"], then execute RUBE_MULTI_EXECUTE_TOOL with the discovered tool slug and proper memory and session_id

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current schemas
Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools
Use exact field names and types from search results
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
Reuse session IDs within a workflow and generate new ones for new runs

Example Use Cases

Automate a monthly Entelligence data consolidation using the latest tool slugs
Orchestrate a multi-tool Entelligence workflow where each step depends on prior results
Validate the active Entelligence connection before running a batch of tasks
Discover available Entelligence tools, then execute a specific tool with provided arguments
Fetch all tool schemas via pagination and run selected tools across multiple sessions

Frequently Asked Questions

Add this skill to your agents