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

SKILL

altoviz-automation

Name: altoviz-automation
Author: Composio

Automate Altoviz workflows via Rube MCP after checking current tool schemas.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

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

Summary

This skill is essentially an instruction wrapper for Rube MCP/Composio, and as a prompt-only artifact from a highly trusted open-source repository, its overall risk is relatively low. The main caution is that it relies on an external MCP service and an Altoviz account connection, so actual data egress and account actions occur on third-party platforms.

CredentialsCaution

The material says no API key is needed, but it requires establishing an `altoviz` connection via `RUBE_MANAGE_CONNECTIONS` and following an auth link when the connection is not active; this implies third-party account tokens or OAuth-style credentials are involved. The skill does not directly collect secrets, but it initiates an external authorization flow, so scope and token handling should be reviewed.

Network egressCaution

The README explicitly requires adding the remote MCP endpoint `https://rube.app/mcp` and using Composio/Rube for search, connection management, and tool execution; user inputs, session IDs, tool arguments, and potentially Altoviz business data may be sent to those external services. The endpoints appear related to the stated function, but they are still a clear third-party network egress path.

Code executionLow risk

Based on the provided material, this is a prompt-only skill description with no bundled install script, local binary, or direct instruction to run commands on the host. Its behavior is mainly to guide external MCP tool calls rather than grant local code execution.

Data accessCaution

There is no indication of requesting local filesystem, system directory, or device permissions; however, once the Altoviz connection is active, `RUBE_MULTI_EXECUTE_TOOL` can perform Altoviz actions on behalf of the connected account and includes session and memory parameters. The main concern is remote account/business-data access rather than excessive local data permissions.

Supply chainLow risk

The source is an open-source GitHub repository with strong community adoption (about 64.7k stars), which are clear risk-reducing signals; the material itself is also just skill text and is fairly auditable. Caveats are the undeclared license, unknown maintenance status, and that the actual Rube/Composio runtime is outside the audit scope of this skill repository.

Recommendations

Review the privacy, retention, and logging policies of Rube MCP and Composio before enabling the integration.
Use a least-privilege Altoviz account for authorization and regularly review/revoke third-party tokens.
Validate `RUBE_SEARCH_TOOLS` and execution behavior in a test environment before using production data or bulk actions.
Log the actual remote domains contacted, transmitted fields, and operation audit trails for traceability.

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 "altoviz-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/altoviz-automation/SKILL.md
2. Save it as ~/.claude/skills/altoviz-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

Altoviz Automation via Rube MCP

Automate Altoviz operations through Composio's Altoviz toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/altoviz

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
Active Altoviz connection via RUBE_MANAGE_CONNECTIONS with toolkit altoviz
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 altoviz
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: "Altoviz 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 Altoviz task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["altoviz"]
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 Altoviz-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `altoviz`
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 Alpha Vantage data queries and workflows through Rube MCP.

ComposioGet→

$ loading_