Do I need API keys to use this skill?

No API keys are needed; just add the MCP server endpoint https://rube.app/mcp in your client configuration.

How do I verify the Wiz connection is ready?

Use RUBE_MANAGE_CONNECTIONS with toolkits: ["wiz"] and check that the status is ACTIVE before running tools.

What if tool schemas change or there are many tools?

Always call RUBE_SEARCH_TOOLS first to fetch current schemas, and handle pagination if the tool list is large; avoid hardcoding slugs or arguments.

wiz-automation

Scanned

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

Files (1)

SKILL.md

2.8 KB

Wiz Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/wiz

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["wiz"]
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 Wiz-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `wiz`
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/wiz-automation/SKILL.mdView on GitHub

Overview

Automate Wiz operations through Composio's Wiz toolkit using Rube MCP. This skill emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS before running workflows and managing Wiz connections for seamless automation.

How This Skill Works

Connect to Rube MCP at the provided endpoint, verify RUBE_SEARCH_TOOLS is responding, and manage Wiz connections with RUBE_MANAGE_CONNECTIONS. Then discover available Wiz tools using RUBE_SEARCH_TOOLS, confirm the connection is ACTIVE, and execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL, supplying the discovered arguments and a memory object along with a session_id.

When to Use It

When you need to perform a Wiz operation but tool schemas may change, so you must discover current tool slugs and schemas first.
When setting up a Wiz workflow from scratch and you want to rely on up-to-date tool schemas rather than hardcoded values.
When you want to reuse a session across multiple Wiz tasks within a single workflow.
When you must verify the Wiz connection is ACTIVE before executing tools.
When handling tool schema changes or pagination to fetch all available Wiz tools before execution.

Quick Start

Step 1: Verify Rube MCP connectivity and Wiz availability by calling RUBE_SEARCH_TOOLS and ensuring it responds.
Step 2: Discover Wiz tools with a Wiz-specific use_case via RUBE_SEARCH_TOOLS and note the TOOL_SLUG and required arguments.
Step 3: Ensure the connection is ACTIVE with RUBE_MANAGE_CONNECTIONS, then execute the tool using RUBE_MULTI_EXECUTE_TOOL, including memory and a session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current Wiz tool schemas.
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before any execution.
Use exact field names and types from the search results; do not hardcode tool slugs or arguments.
Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty ({}).
Reuse session IDs within a workflow and paginate through tool schemas if needed.

Example Use Cases

Automate a Wiz data export by discovering the appropriate tool slug via RUBE_SEARCH_TOOLS, then executing it with the required arguments and a memory object.
Run a Wiz operation by selecting a tool slug from search results and passing the exact schema-compliant arguments returned by the tool discovery.
Chain multiple Wiz tools in a single workflow by reusing a session_id and maintaining connection ACTIVE status throughout.
Before a batch of Wiz tasks, verify the Wiz connection is ACTIVE and then execute tools sequentially using RUBE_MULTI_EXECUTE_TOOL with proper memory and session management.
Paginate through Wiz tool schemas when the Wiz toolbox is large, then choose and execute a suitable tool based on the latest schemas.

Frequently Asked Questions

Add this skill to your agents