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

SKILL

moxie-automation

Name: moxie-automation
Author: Composio

Automate Moxie tasks through 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.9k

Summary

This skill appears to be a prompt/instruction asset in an open-source, highly trusted repository, with no direct local secrets or explicit built-in endpoint, so the artifact itself is low risk. However, its intended use routes actions through Rube MCP and external Moxie integrations, which introduces third-party connectivity and authorization considerations during real use.

CredentialsCaution

The material states there are no API keys, but it requires an ACTIVE `moxie` connection via `RUBE_MANAGE_CONNECTIONS` and setup through a returned auth link. So while the skill itself does not collect local secrets, actual use still depends on third-party account authorization/tokens, creating ordinary concerns around connection misuse or over-scoped access.

Network egressCaution

The README explicitly instructs adding `https://rube.app/mcp` as an MCP server and using Composio/Rube to search tools, manage connections, and execute workflows. Therefore, user requests, session IDs, tool arguments, and potentially business data may be sent to external services as part of normal operation. No unrelated or hidden exfiltration endpoint is shown, but expected third-party network egress exists.

Code executionLow risk

Based on the provided artifact, this is a prompt/instruction asset rather than an executable install script, and it does not declare local process spawning, system command execution, or direct requests for high-risk system privileges. The mentioned `RUBE_MULTI_EXECUTE_TOOL` is a description of external MCP tool use, not evidence that this skill itself has local code execution capability.

Data accessCaution

The skill text itself does not request local file read/write access, but it is designed to perform Moxie operations/workflows through an external toolkit and supports session reuse, bulk operations, and remote workbench patterns. This means the effective data access scope depends on the permissions granted to Rube/Composio and the connected Moxie account, so over-broad authorization should be avoided.

Supply chainLow risk

The source is an open-source GitHub repository with strong community adoption (~64.9k stars), both of which materially lower supply-chain risk. The material also aligns with a prompt-only artifact, making supply-chain risk comparatively low. That said, the README mainly points users to external Rube/Composio services, and the license and maintenance status are not explicit, so those should still be verified before adoption.

Recommendations

Only connect after confirming that `rube.app` and Composio are the intended official services, and review their privacy and data-handling terms.
Use least-privilege authorization when connecting Moxie, and regularly review/revoke integrations or tokens that are no longer needed.
Before production use, test with a non-production account to verify the tool scope returned by `RUBE_SEARCH_TOOLS` and what data is actually transmitted.
Keep session and execution audit logs, and avoid placing unnecessary sensitive business data in tool arguments.

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

// download

Download SKILL.mdInstall manifest ↗

// docs

Moxie Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/moxie

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["moxie"]
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 Moxie-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `moxie`
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 Melo workflows via Rube MCP using current tool schemas first.

ComposioGet→

$ loading_