How do I ensure tool schemas are current?

Always call RUBE_SEARCH_TOOLS before executing; never hardcode tool slugs; optionally consult RUBE_GET_TOOL_SCHEMAS for full details.

How do I know the system is ready to run?

Check that RUBE_MANAGE_CONNECTIONS reports status ACTIVE before executing any tools.

Is memory required in multi tool execution?

Yes, memory must be included in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({}).

plasmic-automation

npx machina-cli add skill ComposioHQ/awesome-claude-skills/plasmic-automation --openclaw

Files (1)

SKILL.md

2.9 KB

Plasmic Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/plasmic

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["plasmic"]
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 Plasmic-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `plasmic`
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/plasmic-automation/SKILL.mdView on GitHub

Overview

Automates Plasmic operations using Composio's Plasmic toolkit through Rube MCP. It emphasizes querying current tool schemas with RUBE_SEARCH_TOOLS before running any workflow to avoid hard-coded slugs. This keeps automation aligned with live Plasmic definitions and reduces setup drift.

How This Skill Works

First, discover available Plasmic tools with RUBE_SEARCH_TOOLS using a Plasmic-focused use_case. Then establish and verify an ACTIVE connection via RUBE_MANAGE_CONNECTIONS for the Plasmic toolkit. Finally, execute the selected tool with RUBE_MULTI_EXECUTE_TOOL, providing the discovered slug, exact schema-compliant arguments, and a memory payload (even if empty).

When to Use It

When you need to automate recurring Plasmic tasks and keep tool schemas current.
When starting a Plasmic automation, to fetch available tools before building workflows.
When validating a pipeline, ensuring the connection is ACTIVE before execution.
When performing bulk operations across multiple Plasmic tools in one session.
When handling tools with pagination or evolving schemas to avoid stale slugs.

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server and verify RUBE_SEARCH_TOOLS.
Step 2: Manage and verify the Plasmic connection via RUBE_MANAGE_CONNECTIONS; confirm ACTIVE.
Step 3: Discover tools with RUBE_SEARCH_TOOLS and execute a tool using RUBE_MULTI_EXECUTE_TOOL with proper arguments and memory.

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas.
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
Use exact field names and types from the discovered schemas.
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty {}.
Reuse session IDs within a workflow and paginate tool responses as needed.

Example Use Cases

Automate a component update by discovering the latest Plasmic tool slug and running it with current args.
Batch-run several Plasmic operations after confirming an ACTIVE connection.
Fetch full tool schemas with RUBE_GET_TOOL_SCHEMAS and incorporate them into a deployment pipeline.
Use RUBE_REMOTE_WORKBENCH with run_composio_tool() to perform bulk Plasmic tasks.
Handle pagination tokens when discovering tools to ensure all options are available.

Frequently Asked Questions

Add this skill to your agents