Do I need API keys to use this skill?

No API keys are needed. Add https://rube.app/mcp as the MCP server in your client configuration.

What should I do if tool schemas change?

Always call RUBE_SEARCH_TOOLS to fetch current tool slugs and input schemas; do not hardcode slugs or arguments.

How can I ensure I’m ready to execute?

Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools, and include a memory payload in RUBE_MULTI_EXECUTE_TOOL calls.

ignisign-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Ignisign Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/ignisign

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Ignisign tasks using Rube MCP and Composio's Ignisign toolkit. The workflow relies on always fetching current tool schemas before execution to adapt to updates.

How This Skill Works

The skill connects to Rube MCP, discovers available Ignisign tools with RUBE_SEARCH_TOOLS, and ensures the Ignisign connection is ACTIVE via RUBE_MANAGE_CONNECTIONS. It then executes the chosen tool with RUBE_MULTI_EXECUTE_TOOL, including a memory payload and a session_id to maintain workflow continuity.

When to Use It

Setting up an Ignisign automation session after connecting to Rube MCP.
Running a signing workflow only after RUBE_SEARCH_TOOLS shows available tools.
Batch-executing actions with RUBE_MULTI_EXECUTE_TOOL within a session.
Validating ACTIVE RUBE_MANAGE_CONNECTIONS before execution.
Integrating Ignisign tasks into a larger Composio-based pipeline.

Quick Start

Step 1: Verify RUBE MCP connection and ensure RUBE_SEARCH_TOOLS responds; use toolkit 'ignisign'.
Step 2: Run RUBE_SEARCH_TOOLS with use_case set to 'Ignisign operations' to discover tools.
Step 3: Run RUBE_MANAGE_CONNECTIONS to confirm ACTIVE status, then RUBE_MULTI_EXECUTE_TOOL with the chosen tool slug and a memory payload.

Best Practices

Always call RUBE_SEARCH_TOOLS before executing to get current tool slugs and schemas.
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before running tools.
Use exact field names and types as returned by the tool schemas.
Always include a memory object in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
Reuse session IDs within a workflow and generate new ones for new workflows.

Example Use Cases

Discover Ignisign tools with RUBE_SEARCH_TOOLS, then execute a signing task using the returned tool_slug and schema.
Establish a connection to Ignisign via RUBE_MANAGE_CONNECTIONS and verify it is ACTIVE before running workflows.
Run a sequence of signing steps with RUBE_MULTI_EXECUTE_TOOL using the discovered slugs and memory payload.
If tool schemas change, re-run RUBE_SEARCH_TOOLS to fetch updated slugs and input schemas.
Within a single automation, reuse the same session_id across multiple tool executions to maintain state.

Frequently Asked Questions

Add this skill to your agents