linguapop-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/linguapop-automation --openclawLinguapop Automation via Rube MCP
Automate Linguapop operations through Composio's Linguapop toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/linguapop
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Linguapop connection via
RUBE_MANAGE_CONNECTIONSwith toolkitlinguapop - 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 toolkitlinguapop - 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: "Linguapop 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 Linguapop task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["linguapop"]
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 Linguapop-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit linguapop |
| 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/linguapop-automation/SKILL.mdView on GitHub Overview
Linguapop Automation via Rube MCP orchestrates Linguapop workflows using Composio's toolkit. It emphasizes discovering current tool schemas first, establishing a valid Linguapop connection, and executing tools with schema-compliant inputs to maintain reliability as schemas evolve.
How This Skill Works
The process starts by calling RUBE_SEARCH_TOOLS to fetch current tool schemas and recommended execution plans. Next, RUBE_MANAGE_CONNECTIONS is used to ensure the Linguapop toolkit connection is ACTIVE. Finally, RUBE_MULTI_EXECUTE_TOOL runs the chosen tool with the discovered slug and proper arguments, always including memory and a session_id to maintain workflow context.
When to Use It
- When you need the latest Linguapop tool schemas before a run.
- When setting up or re-validating a Linguapop connection.
- When executing a discovered tool with exact field names and types.
- When a workflow requires session reuse across steps.
- When performing bulk or batch Linguapop tasks with remote bench.
Quick Start
- Step 1: RUBE_SEARCH_TOOLS with queries: [{use_case: "Linguapop operations", known_fields: ""}] and session: {generate_id: true}
- Step 2: RUBE_MANAGE_CONNECTIONS toolkits: ["linguapop"] and verify session_id; ensure ACTIVE
- Step 3: RUBE_MULTI_EXECUTE_TOOL with tools: [{tool_slug: "TOOL_SLUG_FROM_SEARCH", arguments: {/* schema-compliant args */}}], memory: {}, session_id: "your_session_id"
Best Practices
- Always call RUBE_SEARCH_TOOLS first to pull current tool slugs and schemas.
- Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing.
- Adhere to the exact field names and types from the schema.
- Include memory in RUBE_MULTI_EXECUTE_TOOL payload (even if empty).
- Reuse session IDs for related steps; refresh for standalone workflows.
Example Use Cases
- Discover Linguapop tools with RUBE_SEARCH_TOOLS, connect via linguapop, and execute a content-creation tool in a single session.
- Chain two Linguapop tasks by reusing a session ID within one workflow to maintain context.
- Whenever tool schemas change, re-run RUBE_SEARCH_TOOLS to fetch the new slug and fields before execution.
- Before batch runs, ensure the Linguapop connection is ACTIVE using RUBE_MANAGE_CONNECTIONS.
- Perform bulk Linguapop operations with RUBE_REMOTE_WORKBENCH run_composio_tool() to process multiple tools at once.
