home / skills / composiohq / awesome-claude-skills / textrazor-automation

textrazor-automation skill

safe

/textrazor-automation

This skill automates Textrazor tasks via Composio's Rube MCP, ensuring up-to-date tool schemas are discovered before execution.

npx playbooks add skill composiohq/awesome-claude-skills --skill textrazor-automation

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

2.9 KB

---
name: textrazor-automation
description: "Automate Textrazor tasks via Rube MCP (Composio). Always search tools first for current schemas."
requires:
  mcp: [rube]
---

# Textrazor Automation via Rube MCP

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

**Toolkit docs**: [composio.dev/toolkits/textrazor](https://composio.dev/toolkits/textrazor)

## Prerequisites

- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Textrazor connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `textrazor`
- 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.

1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `textrazor`
3. If connection is not ACTIVE, follow the returned auth link to complete setup
4. Confirm connection status shows ACTIVE before running any workflows

## Tool Discovery

Always discover available tools before executing workflows:

```
RUBE_SEARCH_TOOLS
queries: [{use_case: "Textrazor 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 Textrazor task"}]
session: {id: "existing_session_id"}
```

### Step 2: Check Connection

```
RUBE_MANAGE_CONNECTIONS
toolkits: ["textrazor"]
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 Textrazor-specific use case |
| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `textrazor` |
| 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](https://composio.dev)*

Overview

This skill automates Textrazor tasks through Composio’s Textrazor toolkit using the Rube MCP orchestration layer. It provides a clear workflow for discovering tools, validating connections, and executing Textrazor operations reliably. The skill emphasizes always searching for current tool schemas before running any actions to avoid breaking changes.

How this skill works

First, call RUBE_SEARCH_TOOLS to discover available Textrazor tool slugs, input schemas, and recommended execution plans. Then verify an active Textrazor connection via RUBE_MANAGE_CONNECTIONS. Finally, run one or more tools with RUBE_MULTI_EXECUTE_TOOL (including a memory object) or bulk-run via RUBE_REMOTE_WORKBENCH when needed.

When to use it

Automating text analysis pipelines that rely on Textrazor features (entity extraction, relations, categories).
Building repeatable NLP workflows that must adapt to changing tool schemas.
Running bulk or batched Textrazor jobs via the Rube MCP orchestration layer.
Integrating Textrazor into larger agent-driven or composable automation flows.
Quick validation and dry-run of Textrazor tool inputs and outputs before production.

Best practices

Always call RUBE_SEARCH_TOOLS first; never hardcode tool slugs or argument schemas.
Confirm Textrazor connection status is ACTIVE via RUBE_MANAGE_CONNECTIONS before executing tools.
Include an explicit memory object (even empty {}) in RUBE_MULTI_EXECUTE_TOOL calls.
Reuse a session_id for related steps; generate a new session_id for separate workflows.
Handle pagination tokens from search responses to fetch full result sets.

Example use cases

Discover the current Textrazor entity-extraction tool, validate the connection, and run entity extraction on a batch of documents via RUBE_MULTI_EXECUTE_TOOL.
Set up a scheduled workflow that searches for updated tool schemas, then runs a composio pipeline using RUBE_REMOTE_WORKBENCH for bulk classification.
Perform a quick schema fetch with RUBE_GET_TOOL_SCHEMAS to build a dynamic UI form for Textrazor tool inputs.
Debug a failing Textrazor call by re-running RUBE_SEARCH_TOOLS, checking the connection, and executing a single tool with precise, schema-compliant arguments.

FAQ

What must I always call before executing a tool?

Always call RUBE_SEARCH_TOOLS to fetch current tool slugs and input schemas before running any Textrazor tool.

How do I handle connection setup?

Use RUBE_MANAGE_CONNECTIONS with toolkit 'textrazor' and follow the returned auth link if the connection is not ACTIVE; confirm ACTIVE before proceeding.