Get the FREE Ultimate OpenClaw Setup Guide →

jigsawstack-automation

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

Jigsawstack Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/jigsawstack

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["jigsawstack"]
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 Jigsawstack-specific use case
ConnectRUBE_MANAGE_CONNECTIONS with toolkit jigsawstack
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/jigsawstack-automation/SKILL.mdView on GitHub

Overview

Automate Jigsawstack operations through Composio Jigsawstack toolkit via Rube MCP. This skill guides you to connect Rube MCP, search for current tool schemas, and run tools using a structured workflow.

How This Skill Works

First, discover tools with RUBE_SEARCH_TOOLS to obtain slugs and input schemas. Then connect to the jigsawstack toolkit via RUBE_MANAGE_CONNECTIONS and ensure the status is ACTIVE. Finally, run tools with RUBE_MULTI_EXECUTE_TOOL using the discovered tool slug and the exact arguments from the schema, always including memory and a session_id.

When to Use It

  • Automating recurring Jigsawstack tasks
  • Always search for current tool schemas before running
  • Setting up and validating an ACTIVE jigsawstack connection
  • Orchestrating multiple tools in a single session
  • Handling tool responses and pagination while discovering tools

Quick Start

  1. Step 1: Add the Rube MCP endpoint https://rube.app/mcp as an MCP server and verify RUBE_SEARCH_TOOLS responds
  2. Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkit jigsawstack and authenticate if prompted; ensure status is ACTIVE
  3. Step 3: Discover tools with RUBE_SEARCH_TOOLS and execute a chosen tool via RUBE_MULTI_EXECUTE_TOOL using the slug and exact arguments from the schema; include memory and session_id

Best Practices

  • Always call RUBE_SEARCH_TOOLS first to fetch current schemas
  • Verify RUBE_MANAGE_CONNECTIONS reports ACTIVE before executing tools
  • Use exact field names and types from the search results
  • Include memory in every RUBE_MULTI_EXECUTE_TOOL call
  • Reuse session IDs within a workflow and handle pagination

Example Use Cases

  • Daily Jigsawstack task automation using a discovered tool slug and session management
  • Onboard a new Jigsawstack operation by discovering its schema before execution
  • Batch workflow that runs multiple Jigsawstack tools in one session
  • Dry run by validating arguments against the discovered schema
  • Enumerate all available Jigsawstack tools by handling pagination

Frequently Asked Questions

Add this skill to your agents
Sponsor this space

Reach thousands of developers