PromptShop

Textcortex Automation

automates Textcortex operations using Composio's Textcortex toolkit via Rube MCP.

Install

npx promptshop add textcortex-automation

Details

What This Skill Does

This skill automates Textcortex operations using Composio's Textcortex toolkit via Rube MCP. It allows users to discover available tools, check connections, and execute specific Textcortex tasks, streamlining workflows for content creation and AI-driven tasks.

When to Use

  • Generate marketing copy automatically.
  • Create product descriptions in bulk.
  • Summarize long documents quickly.
  • Translate text into multiple languages.
  • Improve content SEO with keyword analysis.
  • Automate social media post creation.

Key Features

  • Uses Rube MCP for Textcortex automation.
  • Discovers tools via RUBE_SEARCH_TOOLS.
  • Manages connections with RUBE_MANAGE_CONNECTIONS.
  • Executes tools with RUBE_MULTI_EXECUTE_TOOL.
  • Provides toolkit documentation link.
  • Requires active Textcortex connection.

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

OperationApproach
Find toolsRUBE_SEARCH_TOOLS with Textcortex-specific use case
ConnectRUBE_MANAGE_CONNECTIONS with toolkit textcortex
ExecuteRUBE_MULTI_EXECUTE_TOOL with discovered tool slugs
Bulk opsRUBE_REMOTE_WORKBENCH with run_composio_tool()
Full schemaRUBE_GET_TOOL_SCHEMAS for tools with schema Ref