webvizio-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/webvizio-automation --openclawWebvizio Automation via Rube MCP
Automate Webvizio operations through Composio's Webvizio toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/webvizio
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Webvizio connection via
RUBE_MANAGE_CONNECTIONSwith toolkitwebvizio - 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 toolkitwebvizio - 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: "Webvizio 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 Webvizio task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["webvizio"]
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 Webvizio-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit webvizio |
| 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/webvizio-automation/SKILL.mdView on GitHub Overview
This skill automates Webvizio operations through Composio's Webvizio toolkit using the Rube MCP interface. It emphasizes always discovering current tool schemas first to ensure inputs stay up to date, then guides you through connecting, discovering tools, and executing workflows reliably.
How This Skill Works
Verify MCP availability with RUBE_SEARCH_TOOLS, then establish a Webvizio connection via RUBE_MANAGE_CONNECTIONS using the webvizio toolkit. After discovering tool schemas, execute tools with RUBE_MULTI_EXECUTE_TOOL by supplying the discovered tool_slug and a schema-compliant argument payload, including memory and session details.
When to Use It
- Before running any Webvizio workflow, run RUBE_SEARCH_TOOLS to fetch current tool schemas.
- Establish and verify an ACTIVE Webvizio connection using RUBE_MANAGE_CONNECTIONS.
- Discover available tools with RUBE_SEARCH_TOOLS before selecting a tool_slug.
- Execute tools with RUBE_MULTI_EXECUTE_TOOL, including memory and correct arguments.
- Monitor for schema changes and avoid hardcoding slugs or fields; re-run tool discovery after updates.
Quick Start
- Step 1: Add https://rube.app/mcp as an MCP server in your client configuration and verify connectivity with RUBE_SEARCH_TOOLS.
- Step 2: Call RUBE_MANAGE_CONNECTIONS with the webvizio toolkit and ensure the session shows ACTIVE.
- Step 3: Discover tools with RUBE_SEARCH_TOOLS, then execute a tool with RUBE_MULTI_EXECUTE_TOOL using the discovered slug and proper arguments.
Best Practices
- Always call RUBE_SEARCH_TOOLS to obtain the latest tool schemas before execution.
- Ensure RUBE_MANAGE_CONNECTIONS shows ACTIVE prior to running workflows.
- Use exact field names and types from the search results; do not hardcode slugs or args.
- Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
- Reuse session IDs within a workflow and handle pagination tokens when fetching tools.
Example Use Cases
- Discover the Webvizio operations tool set with RUBE_SEARCH_TOOLS and run a scene_update tool using the discovered slug and required arguments.
- Bulk execute multiple Webvizio tools in one session via RUBE_MULTI_EXECUTE_TOOL with a memory payload.
- Reconnect after a network change by verifying ACTIVE status with RUBE_MANAGE_CONNECTIONS before resuming workflows.
- Adapt automation scripts to tool schema changes by re-running RUBE_SEARCH_TOOLS prior to updating tool calls.
- Page through large tool lists by continuing to fetch with RUBE_SEARCH_TOOLS until all results are retrieved.
