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

SKILL

moz-automation

Name: moz-automation
Author: Composio

Automate Moz SEO tasks via Rube MCP using current tool schemas first.

Stars

★ 67,807

Source

GitHub

Updated

2026-07-15

// securityCaution

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

Summary

This skill itself is an open-source prompt-style wrapper with strong community adoption, and it does not directly require local secrets or declare local code execution, so overall risk is relatively low. However, it is designed to connect to remote Rube MCP/Composio services and a Moz account for external tool execution, so network egress, third-party authorization, and supply-chain considerations still warrant attention.

CredentialsCaution

The material says 'No API keys needed,' but it also requires creating an ACTIVE `moz` connection via `RUBE_MANAGE_CONNECTIONS` and completing an auth link, which implies third-party account authorization tokens are involved. The skill does not declare local secrets directly, but there is a standard caution around Moz credentials being held or used via Rube/Composio.

Network egressCaution

The README explicitly requires adding the remote MCP endpoint `https://rube.app/mcp` and using Composio's Moz toolkit for discovery, connection, and execution. This means task inputs, session IDs, and tool execution results may be sent to the stated third-party service. The endpoint is explicit and functionally related, so this is normal remote egress rather than obviously suspicious exfiltration.

Code executionLow risk

The system marks this as `prompt-only`, and the material does not describe installing local executables, spawning processes, or granting shell/system execution rights. Its primary role is to guide use of connected MCP tools rather than directly executing code on the user's machine.

Data accessCaution

The skill itself does not declare local file access or broad access to local data, but it does perform search, connection, and bulk operations on Moz account data through Rube MCP, and it uses session state and a `memory` parameter. This should be treated as normal access to external business data, not excessive local authorization.

Supply chainLow risk

The source is an open-source GitHub repository, the system marks it as `open-source`, and community adoption is very strong (64.7k stars), all of which materially reduce risk. Although the license is unspecified, maintenance status is unknown, and actual operation depends on external Rube/Composio services, the available material does not show a concrete supply-chain red flag.

Recommendations

Before connecting, verify the data handling and authorization scope of `rube.app/mcp`, Composio, and Moz, and grant only the minimum account permissions needed.
Avoid placing unnecessary sensitive data in tool arguments, session content, or memory; minimize inputs whenever possible.
Before production use, inspect the actual tool list and schemas returned by Rube/Composio to ensure only Moz-relevant actions are invoked.
Prefer testing third-party connections and bulk operations in an isolated environment or with a low-privilege account first.

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

// download

Download SKILL.mdInstall manifest ↗

// docs

Moz Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/moz

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["moz"]
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 Moz-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `moz`
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 Yousearch tasks through Rube MCP and chain follow-up workflows.

ComposioGet→

$ loading_