visme-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/visme-automation --openclawVisme 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_CONNECTIONSwith toolkitvisme - Always call
RUBE_SEARCH_TOOLSfirst 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_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkitvisme - 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_CONNECTIONSshows ACTIVE status before executing tools - Schema compliance: Use exact field names and types from the search results
- Memory parameter: Always include
memoryinRUBE_MULTI_EXECUTE_TOOLcalls, 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
Source
git clone https://github.com/ComposioHQ/awesome-claude-skills/blob/master/composio-skills/visme-automation/SKILL.mdView on GitHub Overview
Visme Automation via Rube MCP lets you orchestrate Visme operations using Composio's Visme toolkit. It relies on RUBE_SEARCH_TOOLS to fetch current tool schemas before running workflows. The integration requires a connected Rube MCP and an active Visme connection.
How This Skill Works
You discover available tools with RUBE_SEARCH_TOOLS, then check or establish the Visme connection with RUBE_MANAGE_CONNECTIONS, and finally execute the chosen tool via RUBE_MULTI_EXECUTE_TOOL, including a memory payload. Tool schemas are dynamic; always use the returned field names and types from the discovery results.
When to Use It
- You need to automate a specific Visme operation and must fetch the exact tool slug and schema automatically
- Setting up a new Visme workflow and verifying an ACTIVE connection before execution
- Batch-running multiple Visme tasks in a single session without hardcoding slugs
- When tool schemas may change and you must rely on current schemas from RUBE_SEARCH_TOOLS
- Handling large result lists that require pagination tokens during discovery or execution
Quick Start
- Step 1: Ensure RUBE MCP is added as an MCP server and verify RUBE_SEARCH_TOOLS responsiveness
- Step 2: Call RUBE_MANAGE_CONNECTIONS for toolkit 'visme' and confirm ACTIVE
- Step 3: Discover tools with RUBE_SEARCH_TOOLS, then execute a tool with RUBE_MULTI_EXECUTE_TOOL using the discovered slug
Best Practices
- Always call RUBE_SEARCH_TOOLS first to get current tool slugs and input schemas
- Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before running any workflows
- Use exact field names and types from the discovery results; avoid hardcoding
- Include a memory object in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
- Reuse session IDs within a workflow and generate new ones for new runs
Example Use Cases
- Discover Visme tools with RUBE_SEARCH_TOOLS for an 'Export Presentation' operation and execute via RUBE_MULTI_EXECUTE_TOOL
- Connect Visme toolkit and run a sequence of tools to batch-create design variations
- Run multiple Visme tasks in a single session, reusing session_id across steps
- Validate connection status with RUBE_MANAGE_CONNECTIONS before executing any tools
- Fetch dynamic schemas with RUBE_GET_TOOL_SCHEMAS and implement them in a subsequent RUBE_MULTI_EXECUTE_TOOL call
