$ ~/registry/skill/composiohq-composio-skills-boldsign-automation

SKILL

boldsign-automation

Automate Boldsign tasks and workflows through Rube MCP tool discovery.

Stars

★ 72,707

Source

GitHub

Updated

2026-08-22

// securityLow risk

Prompt only, no code
Open source
Community-trusted· 72.7k

Running security audit…

Credentials
Network egress
Code execution
Data access
Supply chain

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "boldsign-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/boldsign-automation/SKILL.md
2. Save it as ~/.claude/skills/boldsign-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// use cases

Confirm tools and parameters before execution

Before running Boldsign automation, developers or office workers can search for the current tools and schemas to avoid failures caused by field changes. It is useful when workflows must follow the latest interface definitions.

Troubleshoot connection and authorization issues

When a Boldsign workflow cannot run, users can first verify the Rube MCP connection status for the boldsign toolkit. If the connection is not active, the skill can indicate the required authorization step.

Run automation with the standard workflow pattern

Teams can run Boldsign tasks using the pattern of search first, check connection second, and execute last. This helps reuse sessions and reduces errors from schema mismatches.

// docs

AI summary

The documentation explains how to automate Boldsign operations through Composio's Boldsign toolkit via Rube MCP. It covers prerequisites, connection setup and activation, and the standard workflow of searching tools first, checking the connection, and then executing. It also highlights common pitfalls such as schema changes, required memory parameters, session reuse, and pagination, plus a quick reference for search, connection, execution, and bulk operations.

Show full docs ▾

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

// FAQ

What does this skill do?

It uses Rube MCP to access Composio's Boldsign toolkit and automate Boldsign-related operations. The docs emphasize searching for tools first to get the current schema before execution.

What are the prerequisites?

You need Rube MCP connected and `RUBE_SEARCH_TOOLS` available. You also need an active boldsign connection set up through `RUBE_MANAGE_CONNECTIONS`.

Why do I need to search tools every time first?

Because tool schemas can change, and the docs explicitly say not to hardcode tool slugs or arguments. Searching first gives you the current tools, input fields, and recommended execution plan.

Automate Dropbox Sign requests, status checks, and document workflows via Rube MCP.

ComposioGet→

$ loading_