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

SKILL

plasmic-automation

Name: plasmic-automation
Author: Composio

Automate Plasmic tasks through Rube MCP to speed up page and component management.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

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

Summary

This skill appears to be a prompt-style wrapper with no direct local secret requirement or code execution. However, it relies on remote Rube MCP/Composio and Plasmic integrations, so actual data egress and action scope depend on the external connection and granted permissions.

CredentialsCaution

The material says the skill itself needs no API keys, but it requires an active Plasmic connection via RUBE_MANAGE_CONNECTIONS and completing auth through a returned link. So while there are no local env vars, it still involves third-party account authorization and session handling, creating normal token/connection misuse exposure.

Network egressCaution

The README explicitly requires adding the remote MCP endpoint https://rube.app/mcp and using Composio's Plasmic toolkit. User inputs, tool discovery results, and subsequent Plasmic operation data are therefore expected to be sent to those stated remote services. This is declared network use, with no additional unknown egress endpoint evident in the material.

Code executionLow risk

Based on the provided material, this is a prompt/workflow instruction and does not describe running local scripts, spawning processes, or invoking system commands. Its main role is to guide calls to external MCP tools.

Data accessCaution

The skill does not claim direct local file read/write access, but it automates actions against Plasmic resources through external MCP tools and may access or modify whatever Plasmic projects/data the user authorizes. The material does not provide more granular scope details, so least-privilege review is warranted for third-party SaaS access.

Supply chainLow risk

The source is an open GitHub repository with high community adoption (64.7k stars), which is a meaningful risk-lowering signal. The visible skill content is also primarily documentation-like. Although the license is unspecified and maintenance status is unknown, there is no clear red flag such as closed-source hidden exfiltration, unrelated privilege requests, or overtly deceptive behavior in the material.

Recommendations

Enable it only after confirming trust in the rube.app / Composio / Plasmic integration chain and reviewing the actual OAuth scopes.
Prefer a least-privileged Plasmic account or test project so the connection does not touch sensitive production resources.
Review the actual tool schemas and arguments returned by RUBE_SEARCH_TOOLS before execution to avoid mistakes or excessive write actions.
Regularly review and revoke MCP/Plasmic connections and sessions that are no longer needed.

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

// download

Download SKILL.mdInstall manifest ↗

// docs

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

Automate NPM installs, scripts, and package management through Rube MCP.

ComposioGet→

$ loading_