plasmic-automation

Automate Plasmic platform operations through the Rube MCP gateway for structured task execution.

74.2k|8.5k|Updated Oct 17, 2025
One-click install
npx skills add https://github.com/ComposioHQ/awesome-claude-skills --skill plasmic-automation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plasmic-automation
Source: https://github.com/ComposioHQ/awesome-claude-skills/tree/main/composio-skills/plasmic-automation
Command: npx skills add https://github.com/ComposioHQ/awesome-claude-skills --skill plasmic-automation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the manual overhead of navigating the Plasmic interface by providing a programmatic way to execute tasks and manage connections via the Rube MCP gateway.

Core Features & Use Cases

  • Tool Discovery: Dynamically query available Plasmic tools and schemas to ensure accurate execution.
  • Connection Management: Verify and maintain active authentication states for Plasmic toolkits.
  • Workflow Execution: Perform multi-step operations using discovered tool slugs and schema-compliant arguments.

Quick Start

Use the plasmic-automation skill to discover available tools and execute a specific task for my project.

Frequently Asked Questions about plasmic-automation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I discover available Plasmic tools?

Call the RUBE_SEARCH_TOOLS command with a query related to your specific Plasmic task. This returns the necessary tool slugs, input schemas, and execution plans required for your workflow.

How do I verify my Plasmic connection status?

Use the RUBE_MANAGE_CONNECTIONS command with the 'plasmic' toolkit argument. This will return the current connection status and provide an authentication link if the connection is not active.

Can I execute multiple Plasmic tools in one session?

Yes, use the RUBE_MULTI_EXECUTE_TOOL command to run multiple operations. Ensure you reuse the same session ID and include the memory parameter to maintain state throughout the workflow.

What should I do if a tool schema changes?

Always call RUBE_SEARCH_TOOLS before executing any workflow. Tool schemas are dynamic, and hardcoding slugs or arguments without a fresh search can lead to execution errors.