What is Textcortex Automation via Rube MCP?

It is a workflow pattern that automates Textcortex operations through Composio's toolkit using the Rube MCP platform, including discovery, connection management, and tool execution.

Do I always need to search for tools before executing?

Yes. Always call RUBE_SEARCH_TOOLS to obtain current tool schemas because slugs and arguments can change.

What must be included in tool execution calls?

Include memory in RUBE_MULTI_EXECUTE_TOOL and provide a valid session_id; use exact field names and types from the discovered schema.

textcortex-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Textcortex Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/textcortex

Prerequisites

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

Step 2: Check Connection

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

Overview

This skill orchestrates Textcortex operations through Composio's toolkit using Rube MCP. It emphasizes discovering up-to-date tool schemas before each run and validating the active connection to ensure reliable automation.

How This Skill Works

You first verify connectivity and discover current Textcortex tools with RUBE_SEARCH_TOOLS. Then you establish or confirm an ACTIVE connection via RUBE_MANAGE_CONNECTIONS for the textcortex toolkit. Finally, you execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL using the discovered slug and schema-compliant arguments, including a memory payload and a session_id to maintain workflow state.

When to Use It

When starting automation for a Textcortex task, and you need up-to-date tool schemas before execution.
When you must confirm that the Rube MCP connection for the textcortex toolkit is ACTIVE before running any tools.
When you have a discovered tool slug and you want to pass exact, schema-compliant arguments.
When you want to reuse a session ID across a workflow and ensure memory is included in tool calls.
When handling multiple tool schemas or responses, including pagination, and you need to fetch complete results.

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client and verify RUBE_SEARCH_TOOLS responds.
Step 2: Run RUBE_MANAGE_CONNECTIONS with toolkit: 'textcortex' and ensure the connection status is ACTIVE.
Step 3: Discover tools with RUBE_SEARCH_TOOLS, then execute a chosen tool using RUBE_MULTI_EXECUTE_TOOL with memory and a session_id.

Best Practices

Always search for tools first to obtain current schemas; do not hardcode tool slugs or arguments.
Check that the RUBE_MANAGE_CONNECTIONS status is ACTIVE before executing tools.
Use exact field names and types from the search results to avoid schema mismatches.
Include a memory object in every RUBE_MULTI_EXECUTE_TOOL call, even if empty.
Reuse session IDs within a workflow and fetch additional pages if responses are paginated.

Example Use Cases

Automate a Textcortex summarization by discovering the appropriate tool slug and passing schema-compliant arguments.
Set up a Textcortex editing task after establishing a redacted connection and validating the ACTIVE status.
Execute a batch Textcortex operation using RUBE_MULTI_EXECUTE_TOOL with memory and a reused session_id.
Fetch all available Textcortex tools with RUBE_GET_TOOL_SCHEMAS and handle pagination tokens to completion.
Perform bulk Textcortex tasks via RUBE_REMOTE_WORKBENCH using run_composio_tool() for scalable automation.

Frequently Asked Questions

Add this skill to your agents