rosette-text-analytics-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/rosette-text-analytics-automation --openclawRosette Text Analytics Automation via Rube MCP
Automate Rosette Text Analytics operations through Composio's Rosette Text Analytics toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/rosette_text_analytics
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Rosette Text Analytics connection via
RUBE_MANAGE_CONNECTIONSwith toolkitrosette_text_analytics - Always call
RUBE_SEARCH_TOOLSfirst 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_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkitrosette_text_analytics - 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: "Rosette Text Analytics 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 Rosette Text Analytics task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["rosette_text_analytics"]
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_CONNECTIONSshows ACTIVE status before executing tools - Schema compliance: Use exact field names and types from the search results
- Memory parameter: Always include
memoryinRUBE_MULTI_EXECUTE_TOOLcalls, 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 Rosette Text Analytics-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit rosette_text_analytics |
| 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/rosette-text-analytics-automation/SKILL.mdView on GitHub Overview
Automate Rosette Text Analytics operations through Composio's Rosette toolkit using Rube MCP. The workflow emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS before every run and verifying an ACTIVE connection via RUBE_MANAGE_CONNECTIONS. This approach keeps tools up-to-date and executions reliable.
How This Skill Works
First, discover available Rosette tools with RUBE_SEARCH_TOOLS to obtain current tool slugs and schemas. Then, validate or establish an ACTIVE connection with RUBE_MANAGE_CONNECTIONS for the rosette_text_analytics toolkit. Finally, execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL, including memory and session_id per the discovered schema.
When to Use It
- You want to automate a Rosette Text Analytics task using a discovered tool slug and schema
- You must verify tool schemas are current before each run by calling RUBE_SEARCH_TOOLS
- You need to ensure the Rosette connection is ACTIVE via RUBE_MANAGE_CONNECTIONS before execution
- You are orchestrating a multi-tool workflow with RUBE_MULTI_EXECUTE_TOOL and proper memory and session handling
- You’re performing bulk or iterative analyses and want consistent session reuse across runs
Quick Start
- Step 1: Add https://rube.app/mcp as an MCP server in your client configuration (no API keys needed)
- Step 2: Verify RUBE_SEARCH_TOOLS is available to fetch current tool schemas
- Step 3: Manage the Rosette connection with RUBE_MANAGE_CONNECTIONS, then execute tools using RUBE_MULTI_EXECUTE_TOOL with memory and a session
Best Practices
- Always call RUBE_SEARCH_TOOLS before selecting a tool to get the latest slugs and schemas
- Verify the connection status is ACTIVE with RUBE_MANAGE_CONNECTIONS before executing tools
- Use exact field names and types from the search results; avoid hardcoding slugs or args
- Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({})
- Reuse session IDs within a workflow; generate new ones for separate workflows
Example Use Cases
- Automate sentiment analysis on a customer feedback feed by discovering the appropriate Rosette tool, establishing a connection, and executing with a session
- Extract named entities from a batch of legal documents by first discovering tools, then running the chosen slug with memory and session management
- Perform language detection followed by entity extraction in a streaming text pipeline using discovered tool schemas
- Bulk analyze a corpus with RUBE_REMOTE_WORKBENCH using run_composio_tool() to apply Rosette analytics across many texts
- Iterate over multiple rosette_text_analytics tasks, updating tool slugs as schemas shift and reusing sessions for efficiency
