Do I always need to search tools first?

Yes. The tool schemas change, so you must call RUBE_SEARCH_TOOLS to fetch current slugs and inputs before any execution.

How do I confirm the Encodian connection is ready?

Use RUBE_MANAGE_CONNECTIONS with toolkit 'encodian' and verify the status is ACTIVE before running workflows.

What must I include in multi-tool execution?

Always include a memory parameter (even if empty) and provide session_id, tool_slug, and schema-compliant arguments.

encodian-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Encodian Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/encodian

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Encodian operations through Composio's Encodian toolkit via Rube MCP. The skill emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS before execution and follows a core three-step workflow to establish connections, discover tools, and run workflows.

How This Skill Works

First discover available Encodian tools with RUBE_SEARCH_TOOLS to fetch current input schemas. Then verify the Encodian connection is ACTIVE using RUBE_MANAGE_CONNECTIONS. Finally execute the desired tool with RUBE_MULTI_EXECUTE_TOOL, including memory{} and a valid session_id, using the discovered tool_slug and schema-compliant arguments.

When to Use It

When starting an Encodian automation and you need up-to-date tool schemas before building a workflow
When you must ensure the Encodian connection is ACTIVE prior to running any tools
When orchestrating a multi-tool Encodian workflow that benefits from session reuse
When performing bulk Encodian operations and coordinating tools via RUBE_MULTI_EXECUTE_TOOL
When you need to handle schema changes or pagination in tool discovery

Quick Start

Step 1: Get Rube MCP — add https://rube.app/mcp as an MCP server in your client configuration
Step 2: Discover tools — run RUBE_SEARCH_TOOLS with use_case: 'Encodian operations' to fetch current schemas
Step 3: Connect and execute — run RUBE_MANAGE_CONNECTIONS (toolkit: 'encodian'), ensure ACTIVE, then execute tools with RUBE_MULTI_EXECUTE_TOOL using discovered slug and memory: {}

Best Practices

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

Example Use Cases

Automate a document conversion by discovering the Encodian tool slug, then executing the convert_to_pdf tool with proper arguments
Process a batch of files by discovering multiple Encodian tools and running them sequentially with a shared session_id
Validate the Encodian connection and run a metadata extraction workflow on a set of documents
Inspect available Encodian tools via RUBE_GET_TOOL_SCHEMAS and then execute a selected tool
Bulk operations: use RUBE_REMOTE_WORKBENCH to run multiple Encodian tools with run_composio_tool()

Frequently Asked Questions

Add this skill to your agents