PromptShop

Twitch Automation

This skill automates Twitch operations using the Composio Twitch toolkit via Rube MCP.

Install

npx promptshop add twitch-automation

Details

What This Skill Does

This skill automates Twitch operations using the Composio Twitch toolkit via Rube MCP. It is designed for users who want to streamline their Twitch management tasks. The skill allows users to discover available tools, check connections, and execute tools.

When to Use

  • Automate chat moderation tasks.
  • Manage channel points and rewards.
  • Schedule and manage streams.
  • Post automated messages to chat.
  • Get channel information.
  • Manage Twitch connections.

Key Features

Uses Rube MCP to connect to the Twitch toolkit. Requires an active Twitch connection. Discovers available tools using RUBE_SEARCH_TOOLS. Checks connection status using RUBE_MANAGE_CONNECTIONS. Executes tools using RUBE_MULTI_EXECUTE_TOOL. Provides documentation for the Twitch toolkit.

Manual Installation

Twitch 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_CONNECTIONS with toolkit twitch 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 twitch 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

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: {}

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 Twitch-specific use case
ConnectRUBE_MANAGE_CONNECTIONS with toolkit twitch
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

Powered by Composio