What is mural-automation?

A skill to automate Mural tasks via Rube MCP and Composio's mural toolkit.

What do I need before using it?

A connected Rube MCP, an active Mural connection for the mural toolkit, and access to RUBE_SEARCH_TOOLS to fetch tool schemas.

What if tool schemas change?

Always call RUBE_SEARCH_TOOLS to get current tool slugs and arguments; do not hardcode them.

mural-automation

Scanned

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

Files (1)

SKILL.md

2.8 KB

Mural Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/mural

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Mural operations using Composio's Mural toolkit through Rube MCP. This skill streamlines repetitive mural workflows and ensures tool schemas are always current by starting with a tool discovery step.

How This Skill Works

It first discovers available Mural tools with RUBE_SEARCH_TOOLS, then verifies and establishes a Mural connection via RUBE_MANAGE_CONNECTIONS. Finally, it executes the chosen tool with RUBE_MULTI_EXECUTE_TOOL, supplying the required arguments and a memory payload within an active session.

When to Use It

To automate repetitive Mural operations for a project or template creation
When tool schemas change and you need the latest slugs and fields
Before running workflows to ensure the Mural connection is ACTIVE
For bulk mural tasks using RUBE_REMOTE_WORKBENCH and run_composio_tool
When managing sessions and handling pagination in tool results

Quick Start

Step 1: Verify Rube MCP is available by running RUBE_SEARCH_TOOLS
Step 2: Manage connections for the mural toolkit with RUBE_MANAGE_CONNECTIONS and ensure AUTH if needed
Step 3: Discover tools and execute with RUBE_MULTI_EXECUTE_TOOL using memory and a session_id

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current schemas
Check RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools
Use exact field names and types from the search results
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({})
Reuse session IDs within a workflow and handle pagination tokens

Example Use Cases

Discover a tool slug from RUBE_SEARCH_TOOLS and run it to scaffold a new mural with a specified title and layout
Use a discovered tool to update multiple sticky notes across murals in a batch
Establish a mural connection, then execute a sequence of tools in a single session
Perform bulk updates via RUBE_REMOTE_WORKBENCH with run_composio_tool across many murals
Iterate tool schemas with RUBE_GET_TOOL_SCHEMAS to adapt an automation workflow to changes

Frequently Asked Questions

Add this skill to your agents