What prerequisites are needed to use altoviz-automation?

Rube MCP must be connected, RUBE_SEARCH_TOOLS must be available, and an Active Altoviz connection via RUBE_MANAGE_CONNECTIONS with the toolkit 'altoviz' is required.

How do I ensure tool slugs stay up to date?

Always call RUBE_SEARCH_TOOLS to fetch current tool schemas and then use the discovered slugs and exact field names.

Do I need to pass a memory object?

Yes. Include a memory parameter in RUBE_MULTI_EXECUTE_TOOL calls, even if it is empty.

altoviz-automation

Scanned

npx machina-cli add skill ComposioHQ/awesome-claude-skills/altoviz-automation --openclaw

Files (1)

SKILL.md

2.9 KB

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

Source

git clone https://github.com/ComposioHQ/awesome-claude-skills/blob/master/composio-skills/altoviz-automation/SKILL.mdView on GitHub

Overview

Automates Altoviz operations through Composio's Altoviz toolkit via Rube MCP. It prioritizes discovering current tool schemas with RUBE_SEARCH_TOOLS before execution to adapt to changes and avoid hard-coded slugs.

How This Skill Works

The workflow starts by discovering available tools with RUBE_SEARCH_TOOLS, then establishes and verifies a connection using RUBE_MANAGE_CONNECTIONS for the Altoviz toolkit, and finally executes the selected tool with RUBE_MULTI_EXECUTE_TOOL, including a memory payload and a session_id.

When to Use It

Automating a recurring Altoviz workflow end-to-end (e.g., regular dashboards or reports).
When tool schemas may change and you must fetch fresh slugs and input schemas.
When you need to verify that the Altoviz connection is ACTIVE before running workflows.
When orchestrating multiple Altoviz tools in a single workflow (stepwise execution).
When performing bulk or remote tool operations via the Composio remote workbench.

Quick Start

Step 1: Discover tools with RUBE_SEARCH_TOOLS for Altoviz.
Step 2: Establish/verify connection with RUBE_MANAGE_CONNECTIONS for toolkit altoviz.
Step 3: Execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL, including memory and session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas.
Verify ACTIVE status via RUBE_MANAGE_CONNECTIONS before executing tools.
Use exact field names and types from the search results and avoid hardcoding slugs.
Include a memory parameter in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
Reuse session IDs within a workflow; generate new IDs for new workflows.

Example Use Cases

Discover tools, connect to Altoviz, and run a dashboard refresh workflow.
Automate a data export by identifying the tool slug from RUBE_SEARCH_TOOLS and executing it with proper args.
Chain multiple Altoviz tools in a single session, reusing the same session_id.
Perform bulk operations using RUBE_REMOTE_WORKBENCH's run_composio_tool() with discovered tools.
On initial setup, verify RUBE_SEARCH_TOOLS responsiveness and ACTIVE connection before any run.

Frequently Asked Questions

Add this skill to your agents