$ ~/registry/skill/composiohq-composio-skills-textcortex-automation

SKILL

textcortex-automation

Automate Textcortex tasks and workflows through Rube MCP tool discovery.

Stars

★ 73,862

Source

GitHub

Updated

2026-08-29

// securityLow risk

Prompt only, no code
Open source
Community-trusted· 73.9k

Running security audit…

Credentials
Network egress
Code execution
Data access
Supply chain

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "textcortex-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/textcortex-automation/SKILL.md
2. Save it as ~/.claude/skills/textcortex-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// use cases

Safely invoke Textcortex in a workflow

When developers integrate Textcortex into an automation flow, they can first discover the current tools and schemas before execution to avoid failures caused by interface changes.

Build reusable flows for content teams

Content or marketing teams can use Rube MCP to consistently check connection status, reuse sessions, and run Textcortex-related operations with less repeated setup.

Handle bulk runs and pagination

When tasks require bulk execution or paginated results, users can continue fetching additional pages and reuse the same session throughout the workflow.

// docs

AI summary

The README explains how to automate Textcortex operations through Composio's toolkit via Rube MCP. It covers prerequisites, connection setup and authorization, the required pattern of discovering tools with RUBE_SEARCH_TOOLS, checking connection status with RUBE_MANAGE_CONNECTIONS, and executing tasks with RUBE_MULTI_EXECUTE_TOOL. It also highlights key pitfalls such as schema changes, mandatory memory fields, session reuse, pagination handling, and avoiding hardcoded tool slugs or arguments.

Show full docs ▾

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

// FAQ

What does this skill do?

It uses Rube MCP to access Composio's Textcortex toolkit for automating Textcortex-related operations. The docs emphasize searching for tools first, then executing with the returned schemas.

What prerequisites are required?

You need Rube MCP connected and RUBE_SEARCH_TOOLS available. You also need to create and activate a 'textcortex' connection through RUBE_MANAGE_CONNECTIONS.

Why must I search tools first?

Because tool schemas may change, the docs explicitly warn against hardcoding tool slugs or arguments. Searching first gives you the latest fields, execution plans, and known pitfalls.

Automate Docsumo document extraction and processing tasks through Rube MCP.

ComposioGet→

$ loading_