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

SKILL

wiz-automation

Name: wiz-automation
Author: Composio

Automate Wiz security queries, checks, and remediation via Rube MCP.

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 open-source prompt-style wrapper with no direct local secrets or local code execution requirements, and its high community adoption lowers overall risk. However, it is designed to connect to external services via Rube MCP and operate Wiz, so normal concerns around third-party data flow and external authorization still apply in real deployments.

CredentialsCaution

The material says 'No API keys needed' locally, but it also requires establishing an active Wiz connection via `RUBE_MANAGE_CONNECTIONS` and completing an external auth flow. This implies credentials are handled through Rube/Wiz-side authorization rather than local environment variables. No unrelated sensitive secrets are requested, but the storage/handling of third-party OAuth or connection tokens is not described.

Network egressCaution

The skill explicitly depends on the remote MCP endpoint `https://rube.app/mcp` and then uses Composio/Wiz-related capabilities; user inputs, session IDs, tool arguments, and execution results may be sent to those declared services. No obviously unrelated or unknown exfiltration targets are stated, but data does flow through third parties as part of normal operation.

Code executionLow risk

Based on the material, this is a prompt/workflow-style skill and does not claim to start local processes, run local scripts, or request system-level execution privileges. Its 'execution' is primarily remote MCP tool invocation rather than direct local code execution.

Data accessCaution

There is no indication that it reads or writes the local filesystem or local databases; however, through Rube MCP it can access Wiz tooling and perform automation, which may read or modify data/configuration within the authorized Wiz scope. No excessive local permissions are evident, but the effective access scope on the external service side should be reviewed during authorization.

Supply chainLow risk

The source is an open GitHub repository with very high community adoption (64.7k stars), which are strong risk-reducing signals. The material appears to be skill documentation/prompt content rather than a binary payload, and there are no obvious signs of closed-source delivery, suspicious install scripts, or clear injection-style deception. Gaps remain: no declared license and unknown maintenance status, which should be verified.

Recommendations

Before connecting, verify how `rube.app/mcp`, Composio, and Wiz handle data and tokens, and grant only the minimum Wiz permissions required.
In production, log and audit the actual operations triggered through `RUBE_MULTI_EXECUTE_TOOL` to avoid unintended high-impact changes.
Validate the discovery, connection, and execution flow in a low-privilege test tenant before using it in a production environment.
Check repository maintenance activity, release history, and license details, and pin MCP/tool versions where possible.

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

// download

Download SKILL.mdInstall manifest ↗

// docs

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

Automate WakaTime data queries, reporting, and workflow tasks via Rube MCP.

ComposioGet→

$ loading_