home / skills / composiohq / awesome-claude-skills / intelliprint-automation

intelliprint-automation skill

safe

This skill automates Intelliprint tasks via Rube MCP, prioritizing tool schema discovery to ensure up-to-date, reliable automation workflows.

npx playbooks add skill composiohq/awesome-claude-skills --skill intelliprint-automation

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

2.9 KB

---
name: intelliprint-automation
description: "Automate Intelliprint tasks via Rube MCP (Composio). Always search tools first for current schemas."
requires:
  mcp: [rube]
---

# Intelliprint Automation via Rube MCP

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

**Toolkit docs**: [composio.dev/toolkits/intelliprint](https://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.

1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `intelliprint`
3. If connection is not ACTIVE, follow the returned auth link to complete setup
4. 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](https://composio.dev)*

Overview

This skill automates Intelliprint tasks through Composio's Intelliprint toolkit using the Rube MCP protocol. It orchestrates discovery, connection validation, and execution of Intelliprint tools while enforcing schema compliance and session handling. Use it to run single or bulk Intelliprint operations reliably within automated workflows.

How this skill works

The skill first calls RUBE_SEARCH_TOOLS to discover available Intelliprint tool slugs, input schemas, execution plans, and pagination tokens. It then validates or establishes a connection via RUBE_MANAGE_CONNECTIONS for the toolkit "intelliprint" and confirms the connection status is ACTIVE. Finally it executes one or more tools with RUBE_MULTI_EXECUTE_TOOL (or RUBE_REMOTE_WORKBENCH for bulk runs), always supplying schema-compliant arguments, a memory object, and a session_id.

When to use it

Automate repeatable Intelliprint tasks (rendering, batch prints, reports).
Before running any Intelliprint tool to ensure you have current schemas and slugs.
When orchestrating multi-step Composio workflows that require session reuse.
For bulk operations that benefit from RUBE_REMOTE_WORKBENCH and run_composio_tool().
When integrating Intelliprint into CI/CD pipelines or scheduled automation.

Best practices

Always call RUBE_SEARCH_TOOLS first; never hardcode tool slugs or argument shapes.
Verify RUBE_MANAGE_CONNECTIONS reports ACTIVE for toolkit "intelliprint" before executing tools.
Use exact field names and types from the tool schema; follow schemaRef when provided.
Include a memory object (can be {}) in every RUBE_MULTI_EXECUTE_TOOL call.
Reuse session_id across a workflow; generate a new session for new workflows.
Handle pagination: check response tokens and fetch until complete.

Example use cases

Discover and run an Intelliprint rendering tool for a single document using returned schema fields.
Validate and activate an Intelliprint connection programmatically before a nightly batch print job.
Execute a sequence of Composio tools in a session to prepare assets, render, and deliver outputs.
Perform bulk conversions or print runs using RUBE_REMOTE_WORKBENCH with run_composio_tool().
Fetch full tool schemas with RUBE_GET_TOOL_SCHEMAS before building a custom UI or SDK integration.

FAQ

Do I need API keys to use Rube MCP?

No API keys are required when you add https://rube.app/mcp as an MCP server; just ensure your client can reach that endpoint.

What if a tool schema changes during a workflow?

Call RUBE_SEARCH_TOOLS before each logical workflow step and validate schema fields; if schemas change, adapt arguments and re-run search to get updated tool_slug and input shapes.