esignatures-io-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/esignatures-io-automation --openclawEsignatures IO Automation via Rube MCP
Automate Esignatures IO operations through Composio's Esignatures IO toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/esignatures_io
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Esignatures IO connection via
RUBE_MANAGE_CONNECTIONSwith toolkitesignatures_io - Always call
RUBE_SEARCH_TOOLSfirst 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_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkitesignatures_io - 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: "Esignatures IO 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 Esignatures IO task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["esignatures_io"]
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_CONNECTIONSshows ACTIVE status before executing tools - Schema compliance: Use exact field names and types from the search results
- Memory parameter: Always include
memoryinRUBE_MULTI_EXECUTE_TOOLcalls, 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 Esignatures IO-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit esignatures_io |
| 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/esignatures-io-automation/SKILL.mdView on GitHub Overview
Automate Esignatures IO operations through Composio's Esignatures IO toolkit using Rube MCP. This skill emphasizes always searching for current tool schemas before execution and managing connections with RUBE_MANAGE_CONNECTIONS. Prerequisites include a connected Rube MCP and an active Esignatures IO connection.
How This Skill Works
Discover available tools with RUBE_SEARCH_TOOLS to obtain tool slugs and schemas. Then verify the Esignatures IO connection via RUBE_MANAGE_CONNECTIONS and finally run the chosen tool with RUBE_MULTI_EXECUTE_TOOL, supplying the required arguments and a memory object (even if empty).
When to Use It
- Automating recurring Esignatures IO tasks while ensuring tool schemas stay up to date.
- Integrating Esignatures IO actions into an automated workflow and validating ACTIVE connections first.
- Bulk-processing multiple signature requests across many documents.
- Debugging or updating a pipeline after a tool schema change.
- Reusing a single session to compose related Esignatures IO steps without starting new sessions each time.
Quick Start
- Step 1: Discover available Esignatures IO tools with RUBE_SEARCH_TOOLS to get current slugs and schemas.
- Step 2: Verify the Esignatures IO connection with RUBE_MANAGE_CONNECTIONS and ensure ACTIVE.
- Step 3: Execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL, including memory and the proper session_id.
Best Practices
- Always call RUBE_SEARCH_TOOLS first to fetch current tool slugs and schemas.
- Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
- Use exact field names and types from the search results; avoid hardcoding slugs.
- Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty (memory: {}).
- Reuse session IDs within a workflow; generate new IDs only for separate workflows.
Example Use Cases
- Discover the signature creation tool and initiate a signature request for a contract using the discovered slug and required arguments.
- Batch process pending signatures by iterating over tools and executing them with the corresponding schemas.
- Validate the Esignatures IO connection is ACTIVE before launching a workflow that sends multiple signatures.
- Run multiple tools in a single session to complete a full signature pipeline while preserving state in memory.
- Fetch full schemas via RUBE_GET_TOOL_SCHEMAS when tool changes require an update to the automation plan.
