Get the FREE Ultimate OpenClaw Setup Guide →

flexisign-automation

npx machina-cli add skill ComposioHQ/awesome-claude-skills/flexisign-automation --openclaw
Files (1)
SKILL.md
2.9 KB

Flexisign Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/flexisign

Prerequisites

  • Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
  • Active Flexisign connection via RUBE_MANAGE_CONNECTIONS with toolkit flexisign
  • 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.

  1. Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
  2. Call RUBE_MANAGE_CONNECTIONS with toolkit flexisign
  3. If connection is not ACTIVE, follow the returned auth link to complete setup
  4. Confirm connection status shows ACTIVE before running any workflows

Tool Discovery

Always discover available tools before executing workflows:

RUBE_SEARCH_TOOLS
queries: [{use_case: "Flexisign 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 Flexisign task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["flexisign"]
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

OperationApproach
Find toolsRUBE_SEARCH_TOOLS with Flexisign-specific use case
ConnectRUBE_MANAGE_CONNECTIONS with toolkit flexisign
ExecuteRUBE_MULTI_EXECUTE_TOOL with discovered tool slugs
Bulk opsRUBE_REMOTE_WORKBENCH with run_composio_tool()
Full schemaRUBE_GET_TOOL_SCHEMAS for tools with schemaRef

Powered by Composio

Source

git clone https://github.com/ComposioHQ/awesome-claude-skills/blob/master/composio-skills/flexisign-automation/SKILL.mdView on GitHub

Overview

Automates Flexisign operations through Composio's Flexisign toolkit via Rube MCP. It relies on RUBE_SEARCH_TOOLS to fetch current tool schemas and requires an ACTIVE Flexisign connection before workflows.

How This Skill Works

First, discover available tools using RUBE_SEARCH_TOOLS to retrieve current tool slugs and schemas. Then verify an ACTIVE Flexisign connection with RUBE_MANAGE_CONNECTIONS, and finally run tools using RUBE_MULTI_EXECUTE_TOOL with the correct memory and session_id.

When to Use It

  • Discover the latest Flexisign tool slugs and schemas before starting a task.
  • Ensure RUBE MCP connection is ACTIVE prior to workflow execution.
  • Execute a discovered tool with RUBE_MULTI_EXECUTE_TOOL using a valid session.
  • Reuse session IDs across steps within a single Flexisign automation run.
  • Handle updated tool schemas and pagination by re-running RUBE_SEARCH_TOOLS.

Quick Start

  1. Step 1: Run RUBE_SEARCH_TOOLS to fetch Flexisign tool slugs and input schemas
  2. Step 2: Run RUBE_MANAGE_CONNECTIONS with toolkit flexisign and confirm ACTIVE
  3. Step 3: Run RUBE_MULTI_EXECUTE_TOOL with a chosen tool_slug, memory, and your session_id

Best Practices

  • Always call RUBE_SEARCH_TOOLS first to get current tool schemas.
  • Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before any tool run.
  • 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 only generate a new one for a new run.

Example Use Cases

  • Automate a batch of Flexisign asset conversions by discovering tools and executing them in sequence.
  • Validate the connection, then run a sequence of tools to update a design across multiple files.
  • Fetch the latest tool schemas, select a slug, and execute with the proper arguments.
  • Perform bulk operations via RUBE_MULTI_EXECUTE_TOOL with a single session.
  • Handle pagination tokens when listing tools and run several tools in one workflow.

Frequently Asked Questions

Add this skill to your agents
Sponsor this space

Reach thousands of developers ↗