twitch-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/twitch-automation --openclawTwitch Automation via Rube MCP
Automate Twitch operations through Composio's Twitch toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/twitch
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Twitch connection via
RUBE_MANAGE_CONNECTIONSwith toolkittwitch - 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 toolkittwitch - 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: "Twitch 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 Twitch task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["twitch"]
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 Twitch-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit twitch |
| 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/twitch-automation/SKILL.mdView on GitHub Overview
Automate Twitch operations through Composio's Twitch toolkit via Rube MCP. The workflow emphasizes discovering current tool schemas first using RUBE_SEARCH_TOOLS, then executing actions with properly scoped arguments and a maintained session.
How This Skill Works
Set up Rube MCP by adding the MCP endpoint (https://rube.app/mcp) and verify RUBE_SEARCH_TOOLS responds. Establish a Twitch connection with RUBE_MANAGE_CONNECTIONS and ensure the toolkit is active. Discover available Twitch tools with RUBE_SEARCH_TOOLS to get slugs and input schemas, then execute the chosen tool via RUBE_MULTI_EXECUTE_TOOL using the discovered slug, schema-compliant arguments, a memory payload, and a session_id.
When to Use It
- Automating recurring Twitch operations by discovering the appropriate tool and running it with dynamic arguments.
- Setting up a new Twitch integration workflow by first verifying connectivity and available tool schemas.
- Chaining multiple Twitch actions in a single workflow by reusing a session_id across tool executions.
- Migrating to updated tool schemas without hardcoding slugs by always re-fetching schemas before execution.
- Batching several Twitch actions into one run using RUBE_MULTI_EXECUTE_TOOL for efficiency.
Quick Start
- Step 1: Add https://rube.app/mcp as an MCP server in your client config and verify RUBE_SEARCH_TOOLS responds.
- Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkits: ["twitch"] and ensure the connection status is ACTIVE.
- Step 3: Use RUBE_SEARCH_TOOLS to discover available Twitch tools, then execute a chosen tool with RUBE_MULTI_EXECUTE_TOOL, supplying memory and a session_id.
Best Practices
- Always call RUBE_SEARCH_TOOLS before any workflow to get current tool schemas.
- Never hardcode tool slugs or argument names; rely on live schemas from the search results.
- Include the memory parameter in every RUBE_MULTI_EXECUTE_TOOL call, even if empty ({}).
- Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools.
- Reuse session IDs within a workflow; generate new ones only for new workflows.
Example Use Cases
- Discover Twitch tools with RUBE_SEARCH_TOOLS for use_case 'Twitch operations', then execute a tool slug from the results with the required arguments.
- Connect to Twitch via RUBE_MANAGE_CONNECTIONS and run a tool to perform a chat action after confirming ACTIVE.
- Create a reusable workflow by preserving a session_id and sequentially executing multiple discovered tools using RUBE_MULTI_EXECUTE_TOOL.
- Handle tool schema changes gracefully by re-running RUBE_SEARCH_TOOLS to fetch updated slugs and input fields before execution.
- Execute a batch of Twitch actions in one go by chaining tools with RUBE_MULTI_EXECUTE_TOOL and passing a memory payload.
