What is typless-automation and when should I use it?

Typless-automation automates Typless tasks through Composio's Typless toolkit using Rube MCP. Use it whenever you need to run Typless workflows and you must fetch up-to-date tool schemas before execution.

What are the prerequisites to set it up?

Add the Rube MCP endpoint (https://rube.app/mcp), verify RUBE_SEARCH_TOOLS, connect a Typless toolkit via RUBE_MANAGE_CONNECTIONS, and ensure the connection shows ACTIVE before running workflows.

What are common pitfalls to avoid?

Never hardcode tool slugs or arguments; always call RUBE_SEARCH_TOOLS to get current schemas. Ensure the connection is ACTIVE, use exact field names/types from the results, include memory in RUBE_MULTI_EXECUTE_TOOL calls, and reuse session IDs where appropriate. Also watch for pagination in tool discovery.

typless-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Typless Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/typless

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Typless operations through Composio's Typless toolkit via Rube MCP. Always search for current tool schemas before running workflows to prevent drift. This workflow requires an active Typless connection and a connected Rube MCP.

How This Skill Works

First, use RUBE_SEARCH_TOOLS to discover available Typless tools and their input schemas. Then verify the Typless connection with RUBE_MANAGE_CONNECTIONS and ensure it is ACTIVE. Finally, execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL, passing the exact schema-compliant arguments and including the memory field (even if empty) and the session_id from discovery.

When to Use It

When starting a Typless automation, always run RUBE_SEARCH_TOOLS to fetch current tool schemas.
When validating readiness, confirm RUBE_MANAGE_CONNECTIONS reports an ACTIVE typless connection before execution.
When you need a specific workflow, discover available tools for your Typless task using use_case.
When executing, use the exact tool_slug and pass schema-compliant arguments via RUBE_MULTI_EXECUTE_TOOL.
When chaining steps, reuse session IDs across the workflow and include memory for each execute call.

Quick Start

Step 1: Add the MCP endpoint (https://rube.app/mcp) to your client and verify RUBE_SEARCH_TOOLS responds.
Step 2: Run RUBE_SEARCH_TOOLS with a Typless use_case to discover available tools and their schemas.
Step 3: Run RUBE_MANAGE_CONNECTIONS (toolkits: ["typless"]) and, if ACTIVE, execute your chosen tool with RUBE_MULTI_EXECUTE_TOOL, including memory and session_id.

Best Practices

Always search first to get up-to-date tool slugs and input schemas, since tool definitions change.
Check the Typless connection status (ACTIVE) before attempting any tool execution.
Use exact field names and types from the discovery results when constructing tool arguments.
Include the memory parameter in every RUBE_MULTI_EXECUTE_TOOL call, even if empty ({}).
Reuse session IDs within a workflow and handle pagination tokens when discovering tools.

Example Use Cases

Automate invoice processing by discovering the Typless tool for invoices and executing it with the required fields.
Process purchase orders by selecting a Typless tool via RUBE_SEARCH_TOOLS and running it with the correct schema.
Route multi-document tasks by reusing a session and executing multiple tools in sequence.
Handle large document batches by iterating through pagination in RUBE_SEARCH_TOOLS results until all tools are found.
Troubleshoot schema drift by re-discovering tools before re-running a workflow.

Frequently Asked Questions

Add this skill to your agents