$ ~/registry/skill/composiohq-composio-skills-webvizio-automation

SKILL

webvizio-automation

Name: webvizio-automation
Author: Composio

Automate Webvizio tasks through Rube MCP for faster website feedback workflows.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

Prompt only, no code
Open source
Community-trusted· 64.7k

Summary

This skill appears to be an open-source prompt template with strong public/community signals and no obvious high-risk red flags. The main considerations are its reliance on external Rube MCP/Composio services and a connected Webvizio account, which introduces normal remote-call and account-scoped action risk.

CredentialsCaution

No local API key is explicitly required, but the README requires an active Webvizio connection via `RUBE_MANAGE_CONNECTIONS` and possibly completing auth through a returned link. This implies third-party managed connection credentials or session state, creating normal account-scoped misuse exposure, but there is no explicit red flag of requesting plaintext secrets.

Network egressCaution

The README explicitly points to the external MCP endpoint `https://rube.app/mcp` and performs remote tool calls through Composio/Webvizio. User queries, tool arguments, session IDs, and workflow context may be sent to those services. This egress is consistent with the stated function, but it is still a typical remote-service dependency that should be approved by the organization.

Code executionLow risk

Based on the provided material, this is a prompt-only instruction set and does not include auditable local scripts, binary installation steps, or direct local process/system command execution. No elevated local system permissions are requested.

Data accessCaution

The skill is intended to 'Automate Webvizio operations' and act on Webvizio resources through an authorized connection. That means it can access business data and objects within the connected account scope. The material does not show local file read/write or overreaching system-resource access, but the connected account should still be constrained by least privilege.

Supply chainCaution

Positive signals include a GitHub-hosted open-source repository and strong community adoption (64.7k stars), making the skill text itself auditable. However, the license is unspecified, maintenance status is unknown, and actual execution depends on external Rube MCP/Composio services whose server-side behavior and changes cannot be fully audited from the current material, so 'caution' is appropriate rather than 'risk'.

Recommendations

Only connect to `https://rube.app/mcp` in a trusted environment, and review its data-handling and logging policies first.
Use a least-privilege Webvizio account/connection and avoid granting unnecessary project or workspace scope.
Before production use, log and test the exact Rube/Composio tools and parameters this skill will invoke to avoid accidental changes to live data.
Prefer pinned trusted versions or repository snapshots, and monitor upstream README, connection flow, and remote-service behavior for changes.

Audited by: gpt-5.4 · 2026-06-17

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "webvizio-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/webvizio-automation/SKILL.md
2. Save it as ~/.claude/skills/webvizio-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

Webvizio 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_CONNECTIONS with toolkit webvizio
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 webvizio
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_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

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

Automate Pilvio tasks through Rube MCP using current tool schemas first.

ComposioGet→

$ loading_