What is Boldsign Automation via Rube MCP?

It is a workflow pattern that automates Boldsign tasks through Composio's Boldsign toolkit using the Rube MCP, starting with tool discovery and ending with tool execution.

Do I need API keys to use this skill?

No API keys are needed. Add the Rube MCP server (https://rube.app/mcp) as an MCP source, then rely on RUBE_SEARCH_TOOLS to fetch current tool schemas and RUBE_MANAGE_CONNECTIONS to activate Boldsign.

How do I keep tool schemas up to date?

Always run RUBE_SEARCH_TOOLS before executing any tool to fetch current schemas. For full schema details, you can also use RUBE_GET_TOOL_SCHEMAS. Handle pagination as needed to complete discovery.

boldsign-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Boldsign Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/boldsign

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Boldsign operations through Composio's Boldsign toolkit via Rube MCP. Always search for current tool schemas before running workflows to ensure correct inputs, and maintain an active Boldsign connection throughout. This approach keeps Boldsign automations resilient to schema changes and connection status fluctuations.

How This Skill Works

The skill discovers available Boldsign tools with RUBE_SEARCH_TOOLS, then verifies the Boldsign connection with RUBE_MANAGE_CONNECTIONS. Once a valid tool slug is identified, it executes the tool using RUBE_MULTI_EXECUTE_TOOL, supplying the required arguments and a memory payload, all within an active session.

When to Use It

You’re starting a Boldsign workflow and need up-to-date tool schemas before execution.
You’ve just connected or reconnected the Boldsign toolkit and want to begin work.
You need to run a discovered Boldsign tool with the exact field names from the chosen schema.
You want to perform bulk or chained Boldsign actions via a single orchestration.
You’re debugging or auditing tool schemas, sessions, or pagination during tool discovery.

Quick Start

Step 1: Verify RUBE_SEARCH_TOOLS is available and discover Boldsign tools.
Step 2: Connect Boldsign with RUBE_MANAGE_CONNECTIONS and confirm ACTIVE.
Step 3: Execute a discovered tool using RUBE_MULTI_EXECUTE_TOOL with memory and session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS before executing any Boldsign tool to fetch current schemas.
Verify the Boldsign connection shows ACTIVE using RUBE_MANAGE_CONNECTIONS before running tools.
Use the exact field names and types from the tool schemas returned by the search.
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
Reuse session IDs within a workflow and handle pagination tokens until complete.

Example Use Cases

Discover Boldsign tools with RUBE_SEARCH_TOOLS, pick a signing operation, and execute it via RUBE_MULTI_EXECUTE_TOOL using the discovered slug and required arguments.
Reconnect the Boldsign toolkit and start a signing workflow in an existing session with RUBE_MANAGE_CONNECTIONS and RUBE_MULTI_EXECUTE_TOOL.
Bulk sign multiple documents using RUBE_REMOTE_WORKBENCH and run_composio_tool to orchestrate several Boldsign tools in sequence.
Fetch full tool schemas with RUBE_GET_TOOL_SCHEMAS to audit inputs and update automation logic.
Build a multi-step workflow to sign several documents and monitor status across documents using Boldsign and Composio.

Frequently Asked Questions

Add this skill to your agents