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

SKILL

visme-automation

Name: visme-automation
Author: Composio

Automate Visme tasks through Rube MCP to speed up design workflows.

Stars

★ 67,807

Source

GitHub

Updated

2026-07-15

// securityCaution

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

Summary

This skill appears to be an open-source prompt-style wrapper, but it explicitly depends on remote Rube MCP/Composio services and external Visme connections, so it should be treated as caution rather than high risk. The material does not require local API keys or show local code execution or broad file access, but task inputs and connection-related data are sent to a third-party MCP platform.

CredentialsCaution

The material says 'No API keys needed,' but it requires creating and activating a Visme connection via `RUBE_MANAGE_CONNECTIONS`, implying authentication is handled externally by Rube/Composio. No local plaintext secret is requested, which lowers risk versus direct credential collection, but third-party delegated account access still needs caution.

Network egressCaution

The README explicitly requires adding the remote MCP endpoint `https://rube.app/mcp` and references `composio.dev` docs; tool search, connection management, and execution will send task content, arguments, session IDs, and connection status to those external services. This is typical egress for this kind of tool, with no unrelated or hidden endpoints shown in the material.

Code executionLow risk

The system marks it as `prompt-only`, and the material does not describe installing local executables, shell access, script execution, or system-level command capability. The visible content looks like workflow guidance rather than a local execution component.

Data accessCaution

There is no indication of direct access to local files or system data, but the stated purpose is to 'Automate Visme tasks' through an external connection, meaning workflow inputs, project content, or object metadata may be handled by third-party services. The material does not show excessive local data permissions beyond the Visme automation purpose.

Supply chainLow risk

The source is an open GitHub repository, and the system reports `open-source` with strong community adoption (64.7k stars), which are meaningful positive signals. Although the license is undeclared and maintenance status is unknown, and the skill also depends on the security of external Rube/Composio services, the current material does not justify a high-risk rating.

Recommendations

Before connecting, verify the privacy, retention, and logging policies of `rube.app/mcp` and Composio, and send only the minimum data needed for the Visme task.
Use a least-privilege Visme account for the connection, and regularly review or revoke authorizations created through `RUBE_MANAGE_CONNECTIONS`.
Do not include unnecessary sensitive text, customer data, or long-lived secrets in tool discovery or execution arguments.
Prefer reviewing the open-source repository contents and keep watching upstream maintenance status and changes in the external service.

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

// download

Download SKILL.mdInstall manifest ↗

// docs

Visme Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/visme

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["visme"]
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 Visme-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `visme`
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 Altoviz workflows via Rube MCP after checking current tool schemas.

ComposioGet→

$ loading_