What is Intelliprint Automation via Rube MCP?

It automates Intelliprint tasks through Composio's toolkit using Rube MCP, and requires tool discovery before execution.

Do I need to search tools first every time?

Yes; tool schemas can change, so avoid hardcoding slugs or arguments and always fetch current schemas.

What should I verify before running tools?

Confirm that RUBE_MANAGE_CONNECTIONS shows ACTIVE, ensure the correct session_id is used, and include a memory parameter in RUBE_MULTI_EXECUTE_TOOL; reuse sessions where appropriate.

intelliprint-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Intelliprint Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/intelliprint

Prerequisites

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

Step 2: Check Connection

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

View on GitHub

Overview

Automate Intelliprint operations using Composio's Intelliprint toolkit through Rube MCP. Always fetch current tool schemas with RUBE_SEARCH_TOOLS before running workflows, and ensure an active Intelliprint connection.

How This Skill Works

The skill discovers available tools with RUBE_SEARCH_TOOLS to obtain tool slugs and schemas, establishes an active connection via RUBE_MANAGE_CONNECTIONS, and then executes the selected tool with RUBE_MULTI_EXECUTE_TOOL, including memory and a session_id for continuity.

When to Use It

When setting up a new Intelliprint workflow and you need current tool schemas.
When running a scheduled nightly or batch Intelliprint operation that depends on dynamic tool schemas.
When a tool schema changes and you must revalidate tool slugs and required fields.
When chaining multiple Intelliprint steps in a single session and reusing session IDs.
When validating connections to ensure RUBE_MANAGE_CONNECTIONS shows ACTIVE before execution.

Quick Start

Step 1: Get Rube MCP: add https://rube.app/mcp as an MCP server in your client configuration.
Step 2: Verify RUBE_SEARCH_TOOLS responds and connect: call RUBE_MANAGE_CONNECTIONS with toolkit 'intelliprint' and ensure ACTIVE status.
Step 3: Discover and execute: use RUBE_SEARCH_TOOLS to find tools, then RUBE_MULTI_EXECUTE_TOOL with memory and a session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS before selecting a tool slug.
Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE prior to execution.
Use exact field names and types from the discovered tool schemas.
Include memory (even if empty) in every RUBE_MULTI_EXECUTE_TOOL call.
Reuse session IDs within a workflow; generate new ones for new workflows.

Example Use Cases

Schedule a nightly Intelliprint batch by discovering tools with RUBE_SEARCH_TOOLS and executing a chosen tool slug with proper arguments.
Migrate an existing workflow after a schema change by re-discovering tools and updating required arguments.
Debug a failed run by verifying ACTIVE connection and correct session_id before execution.
Run multiple tools in a single workflow using RUBE_REMOTE_WORKBENCH with run_composio_tool across a session.
Perform bulk updates by discovering tools and executing with memory and strict schema adherence.

Frequently Asked Questions

Add this skill to your agents